Lmst

How to use FSFE's webpreview for translations

Когда‐то давно, но не очень давно, люди, работающие над HTML, всё‐таки решились и запилили элемент <details> для спойлеров. Но есть нюанс: в параграф, куда его очень часто и хотелось бы запихать, его не поместить — парсер выплюнет наружу. А вот в XHTML такой фигни с парсингом не было и нет 🤭

<p>Вот что я тебе скажу, птичка: <details>Спойлерный текст.</details></p>

превращается в:

<p>Вот что я тебе скажу, птичка: </p>
<details>Спойлерный текст.</details>
<p></p>

Так и живём.

А, и да. Текст по умолчанию (когда нет <summary>) не локализуется. Чтобы не расслаблялись 🤷

#lang_ru #html #xhtml

If you’re in the mood for XHTML today, check out @frontenddogma’s XHTML archives! ❎

https://frontenddogma.com/topics/xhtml/

#webdev #xhtml

Markup Languages, by @j9t [@frontenddogma.com]:

https://meiert.com/en/blog/markup-languages/

#overviews #linklists #sgml #html #xml #xhtml #hdml #dhtml #mathml #wml #chtml

@jpmens

Not only that, the source is hand-edited XHTML https://github.com/standardebooks/jane-austen_pride-and-prejudice/blob/master/src/epub/text/chapter-1.xhtml

How quaint!

#XHTML #NoJavaScript #Smallweb

Your eyes haven’t bled from bad markup until they’ve glanced upon an ePUB exported from InDesign.

#ePub #markup #InDesign #XHTML #HTML

Screenshot of code starting with highlighted h4 tag: <h4 class="CHead"><em class="Emphasis">Mys</em><span class="NoBreak"><em class="Emphasis">tery</em></span><span class="NoBreak"><em class="Emphasis"> meat </em></span></h4><p class="BodyFirstParagraph">Every now and again, I come across an “alternative” navigation where a designer has decided they can subvert existing conventions and provide someone with a

The weirdest CSS selector I've used today:

:root[*|xmlns*="facturaElectronica" i]:before

#xml #css #xmlcrimes #csscrimes #xhtml

We should have some markup for Venn diagrams so we don't have to attach them as images when creating memes.

#fediverse #xhtml #unicode

I was wondering why I my #browser is not processing the ENTITY include in my #XHTML's DOCTYPE, so I looked around and found this: https://bugzilla.mozilla.org/show_bug.cgi?id=22942, https://bugzilla.mozilla.org/show_bug.cgi?id=69799

What a shame, this could've been an alternative to the current methods of including HTML templates to a document, which are doing the include server-side and in build-time, JavaScript, and iframes, all of which have trade-offs... Why can't I just include HTML like I can do with CSS stylesheets :(

#XML

If you want to know at what junction our field stood at some point wrt the mobile Web, check out this particular gem from ZDNet, “Souping Up Wireless” (2001).

And yes—WML, HDML, CHTML, XHTML.

Fantastic.

(This relates to what I wrote about the other day, researching content for the 2000s and 2010s archives on @frontenddogma. Stay tuned!)

https://web.archive.org/web/20010609063403/https://www.zdnet.com/eweek/stories/general/0,11011,2766211,00.html

#mobile #wml #hdml #chtml #xhtml #html

@jakintosh I kinda lost interest when #HTML5 came out and was presented as the pragmatic answer to the strictly validated #XHTML. With that we lost namespaces. Sure #RDFa introduced it somewhat, but in an ugly way. I was hoping the future would be <title><dc:title>My blog</dc:title></title>, where RDF would just be mixed in with #HTML. So yeah, also SVG embeds would have been namespaced when mixed in HTML docs. RDFa was supposed to be a pragmatic variant but made metadata a second class citizen. JSON LD is basically the old approach of linking outside for metadata, which is perhaps the worst… so I am now like. Call me when XHTML2 is a thing 😅

Wait, so does XHTML automatically enforce correct element categories|nesting (e.g. stopping you from putting a <li> outside of a <ul>|<ol>)?

#HTML #XHTML

Here's an idea -- why not use declarative files to define program extensions instead of letting extensions run any code whatsoever?

I feel like the whole X/HT/ML era has been completely lost and app developers can't think in anything but code any more. Every problem is solved with JavaScript. Problems with #JS are solved with more JS. Security problems with executing 3rd party code are not solved by removing 3rd party code but trying to naively sandbox the 3rd party code like the halting problem isn't a thing.

#html #xhtml #xml

Still think XHTML(5) is better than HTML(5) :blobcatcoffee:

#lang_en #xhtml #html #web

Latest version of #HTML standard includes a warning that advises against using the #XML syntax (formerly known as #XHTML), stating that it's "essentially unmaintained"🧐 :

https://html.spec.whatwg.org/multipage/xhtml.html

Looks like a recent change, as there's no mention of this in the April 3 version of the spec:

https://web.archive.org/web/20240403210532/https://html.spec.whatwg.org/multipage/xhtml.html

Unless I'm misreading it, this seems like a big deal? E.g. XML syntax is mandatory in #EPUB 3 documents:

https://www.w3.org/TR/epub-33/#dfn-xhtml-content-document

Time to #wheelOutTheDigitalDarkAgeKlaxon 📯?