The more I learn about the #WHATWG the more I grow convinced that they're a horrible steward for the web.
#whatwg
1 post1 participant0 posts today
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 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
FLOSS.socialIgalia (@igalia@floss.social)Attached: 1 image
🎙 New Episode of Igalia Chats: RIP XSLT?
Igalia's @bkardell@toot.cafe and @Meyerweb@mastodon.social chat with Liam Quin about a recent issue in WHATWG regarding the removal of XSLT
https://www.igalia.com/chats/xslt-liam
#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
ilo.imNo, Google Did Not Unilaterally Decide to Kill XSLTThe Web Discourse has been spicy of late, and XSLT is to blame. Well, sort of. It’s complicated.
So, since #Google and #WHATWG removing support of "obsolete" 
#XSLT from their browsers — I remove support of their browsers in the nice looking page with my #RSS (Atom) feed, lol 
On these browsers the feed.xml will looks like on the 1st image. Then on the proper browsers the feed.xml will looks like on the second image
Replied in thread
Continued thread
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
wokGoogle is killing the open webThe juggernaut is taking advantage of its dominant position to enclose and destroy the commons.
#Google #Chrome #WHATWG #XSLT #XML
https://github.com/whatwg/html/pull/11563
IMO this PR is a bad idea and should be closed without merging. XML is a thing in the enterprise world, and XSLT is a useful tool for manipulating it in front-end applications. It's pretty clear from reactions that Google is the *only* party that wants to remove XSLT, and that only to make RSS unusable (RSS conveniently bypasses Google's advertising).
GitHubRemove mentions of XSLT from the html spec by mfreed7 · Pull Request #11563 · whatwg/html
Oh, quelle surprise #whatwg a fermé la discussion sur le ticket concernant la suppression du support de #XSLT. Le roi est nu. Depuis des années, les grands éditeurs de navigateurs se sont évertués à dégrader le support de #XML sur la plateforme du #web. Il n’est plus possible de le cacher. https://github.com/whatwg/html/issues/11523#event-19173131784
GitHubShould we remove XSLT from the web platform? · Issue #11523 · whatwg/html
Google started a WHATWG discussion for removing XSLT. Google has done their best to remove good tech from standards many times.
Responders raised issue with the motive for this change, as opposed to upgrading from XSLT 1.x to 3.1 which would fix all sorts of issues, etc.
Any posts that brought up Google's history and motives were marked as off-topic, and the thread was eventually locked by WHATWG.
GitHubShould we remove XSLT from the web platform? · Issue #11523 · whatwg/html
Continued thread
Also apparently pointing out the facts about #Google's decades-long efforts to destroy the #openWeb and the lies about implementors not having the resources to support modern XSLT is considered a violation of the #WHATWG Code of Conduct.
Reminds me of the failed post.news rules prohibiting «discrimination based on net worth».
When you have to hide the truth to push your agenda, you're not on the right side of history.
3/n
Continued thread
The #WHATWG has become the front through which #Google imposes its will on what is allowed on the web and what isn't. With #Mozilla lacking the backbone (and probably also the intention) to oppose them and #Apple aligned more often than not, it serves no other purpose but to pretend that it's not “what Google says, goes”.
1/n
Continued thread
Why does that matter? Because the #WHATWG using #Chrome usage statistics to determine whether or not a feature is being used or not is just another indication of how strong #Google's stranglehold on the web is.
And while we're at it, for all we know Google might be actively demoting sites that use #XSLT in their searchers, thereby making it even harder for any user to come across such a site. Let's not forget that they've been trying to kill anything XML related for more than a decade.
Continued thread
Progress update on my #XSLT #SVG #sparkline generator
https://wok.oblomov.eu/tecnologia/plotting-sparklines-xslt/
Another step in my path to revitalize usage of XSLT on the web. And before you ask, no, this is not to spite the #WHATWG and their #XML-aversive #JavaScript brainrot, it's something I've wanted to do for years, as documented by my previous posts on the subject.
However, since the corporate-controlled WHATWG is using metrics as excuse to boycott the #openWeb and #indieWeb, it becomes doubly important to do this now.
wokPlotting sparklines with XSLTUsing XSLT to generate sparklines, Wok style
You'd think Google, having launched schema.org, knows how to produce valid schema.org metadata and HTML5.
YouTube: How about a `<span>` inside the head, and `<link rel=alternative>` inside the body?
HTML5 parsers:
Thanks, I'll take that span as your implied end of `<head>`, and raise you an implied start of `<body>`. Everything that follows is now part of the body.
Context:
https://github.com/Ranchero-Software/NetNewsWire/issues/902#issuecomment-2990075755
GitHubFeature request: construct feed URLs for YouTube channels · Issue #902 · Ranchero-Software/NetNewsWire
Interview with Mike Smith from the @w3c about his work on the Ladybird browser
#LadyBird #Webstandards #W3C #accessibility #WHATWG
https://html5accessibility.com/stuff/2025/01/27/ladybird-and-the-old-world-boulevardier/
html5accessibility.comLadybird and the old-world boulevardier – HTML Accessibility
