#whatwg — Public Fediverse posts

RE: https://toot.cafe/@bkardell/116765812688327253

This would be awesome. Including date JS libraries everywhere for this functionality is a pain.

It's also something that would help BackflipHTML tremendously, since it's focused on server-side rendering how to hande dates was nagging at me. Maybe I can just let the spec folks solve that for me... 😛

#html #js #whatwg

@bkardell visits the Fireside

"Brian works at Igalia, he is a member of the W3C Technical Architecture Group (TAG). He also paints many and varied subjects and writes thoughtfully about Web Standards."

https://html5accessibility.com/stuff/2026/06/11/brian-kardell-visits-the-fireside/

#accessibility #webStandards #W3C #WHATWG #Igalia

Ehem, #JavaScript also uses the backslash as a separator in the URL.pathname, like '/'. Firefox dev console, but node is similar:

% let a = new URL("http://localhost/abc\\def")
> undefined
% a.pathname
> "/abc/def"

Can anyone point to a spec where this is described?

#mdn #whatwg

What a “good” #website does….

#WHATWG, #W3C, #IETF #RFCs, #WCAG, #MDN

https://specification.website

ROTFL

#Rust core team listens to Rust developers like the #GAFAM-controlled #WHATWG listens to web developers

#LLM #XSLT #genAI

Have you folks noticed how the recent stream of #JavaScript-related security issues in browsers has NOT resulted in a call from #Google to expunge #JS from the “web platform” as it was done for #XSLT?

#WHATWG #hypocrisy #hypocrites #openWeb #indieWeb

This, by the way, is the reason why my response to the news of the #WHATWG moving forward with the forced removal of #XSLT is

DO NOT COMPLY

https://wok.oblomov.eu/tecnologia/google-killing-open-web-2/#do.not.comply.

(I'll add to that: visit XSLT-using websites often. Blow those stats.)

For starters, most of what the #WHATWG is working on is largely irrelevant for the “web of documents”. This means largely no development efforts to “run after the latest revision of the spec”. I would expect most of the work to be of the maintenance kind (fixing bugs, security issues, and the like), which is sadly the kind of brutal, unglamorous work nobody wants to do.

22/

The #PaleMoon developers should join the #WHATWG just to throw a wrench in their bullshit machinations.

This looks like an excellent opportunity to tell #Mozilla (and hopefully the whole #WHATWG) to prioritize the #openWeb and #indieWeb over the corporate-controlled crapola they are pushing to transform the web into an OS they control: https://interop-rank.jakearchibald.com/

Of course my top votes went to #XSLT3 #JPEGXL #MathML and #SVG. https://wok.oblomov.eu/tecnologia/google-killing-open-web/ —pity none of the points are about #RSS or #SMIL though.

h/t to @dneto and @slightlyoff for bringing this into my timeline.

#XSLT #webDev

The more I read the #XHTML2 spec the more my despise for the #WHATWG grows.

Did you know that XHTML2 had client-side includes, with fallback?

The more I learn about the #WHATWG the more I grow convinced that they're a horrible steward for the web.

A pamiętacie, jak na stronach internetowych dawało się plakietki, że są zgodne ze standardem #HTML, i to było spoko? Za czasów #W3C i otwartych standardów?

Dziś wstydzę się używać HTML-a: standardu, który kiedyś dążył do zgodności, a dziś jest pod całkowitą kontrolą #GAFAM, i służy ich własnym, nikczemnym interesom. Dziś raczej należałoby wstawić banner ze środkowym palcem dla #WHATWG.

Remember back when websites having badges that they conform to #HTML standards was cool? Back in the good old days of #W3C and #OpenStandards?

These days, I'm ashamed of using HTML: the standard that used to mean interoperability, and now is entirely controlled by #GAFAM and used to pursue their own malicious interests instead. Today, the right kind of banner is to show a middle finger to #WHATWG.

Évidemment ce n’est pas RIP #XSLT puisque les navigateurs étaient déjà 20 ans en retard sur les versions du langage. Mais cela parle de la plateforme du Web et des pratiques délétères des éditeurs de navigateurs qui avec #WHATWG se sont emparés des standards du web avec l’abandon complice du #W3C ces dernières années. #www
https://floss.social/@igalia/115066707921700628

This took a lot of effort to overcome my perpetual imposter syndrome, but I wanted to make a comment in support of updating XSLT support in browsers. I figure 18 years working with XML and HTML gives me at least some reasonable experience worth sharing. #XSLT #XML #WHATWG

https://github.com/whatwg/html/issues/11578#issuecomment-3217237081

#Development #Debates
Google did not decide to kill XSLT · What’s happened and what might lie ahead https://ilo.im/166byl

_____
#Styling #RSS #XSLT #Google #WHATWG #WebStandards #WebPlatform #Browser #WebDev #Frontend

Diese #XSLT-Hasser von #WHATWG & Co. haben vermutlich nie ernsthaft damit gearbeitet. Sollten sich schämen und besser 26 Jahre nach 1.0 aktuelle Standards, also XSLT 3.0 und XPath 3.1, implementieren. 👎

@Lukew Because the people at #WHATWG are idiots. A quick look at #XForms, which dates back to 2007, is quite enlightening in this regard. How many years of technological delay has the web platform accumulated because of browser vendors?

This is apparently my life now. I've updated the article AGAIN

https://wok.oblomov.eu/tecnologia/google-killing-open-web/

Added a mention #ManifestV3 and how it might (now or a future change) affect the development of extensions to compensate for the removal of native support for #XSLT .

And since I've apparently hit the news, I've prepared three canned responses for the most frequent objections. In particular, if you're OK with this change because “XML sucks”, YOU ARE #MissingThePoint

#Google #WHATWG #openWeb #indieWeb