mastodon.ie is one of the many independent Mastodon servers you can use to participate in the fediverse.
Irish Mastodon - run from Ireland, we welcome all who respect the community rules and members.

Administered by:

Server stats:

1.6K
active users

#xhtml

0 posts0 participants0 posts today

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!)

web.archive.org/web/2001060906

web.archive.orgZDNet: eWEEK: Souping up wireless
#mobile#wml#hdml
Replied in thread

@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 😅

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.

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"🧐 :

html.spec.whatwg.org/multipage

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

web.archive.org/web/2024040321

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

w3.org/TR/epub-33/#dfn-xhtml-c

Time to #wheelOutTheDigitalDarkAgeKlaxon 📯?

html.spec.whatwg.orgHTML Standard

I guess the #fediverse is probably the best place to ask a #webdev #web functioning question of this nature:

I want to add either an #rss or #atom feed to my personal #website. I'm living like it's 2003 and remade it in #xslt, so I was wondering if there is a way of embedding either format directly inside a #xhtml document, #microdata style, or do I need a separate file and/or a more involved #webserver setup with #contenttype?

That would be swell since I could use the same #xml base file to generate links to posts in the #html document, as well as make it available as a #feed.

The alternative would be to pipe this through some build step that pre-generates both files for me, but I'd rather keep this fully #static "drop files into a web server".

Ffs I’ve spent all day yesterday and all day today trying to get some text in SVG to be clickable and make it make a foreignObject (containing an object with XHTML in it) appear or not appear, there’s so many things impeding any of this from occurring and it’s impossible to figure out why none of it works

I used to be better at SVG than this

(plus, every time I see foreignObject I laugh)
#SVG #foreignObject #XHTML