@neauoire

:drake_no: | fixing websites to work in browsers
:drake_yes: | waiting for browsers to deploy fixes so they work with your website

@cadence did it :> thanks for the inspiration.

https://merveilles.town/web/statuses/105653937278356624

@neauoire Ah, yes. Web rabies. It spreads rapidly and creates an insatiable thirst. Almost always kills the web

@neauoire this reminds me https://yro.slashdot.org/story/21/01/31/2321238/to-re-enable-flash-support-south-africas-tax-agency-released-its-own-web-browser

@neauoire y a les même pour googlestreet map et youtube.

@neauoire nothing to see here, web is not broken

@neauoire wow, this whole C++ file is amazing. Thanks for sharing!

@neauoire interestingly, Firefox has a similar system, but mostly for user agent sniffing counter measures, see about:compat. I guess it's a game you have to play if you're not Chrome 😔

@neauoire The iCloud stuff is the most embarrassing because that’s Apple’s own site.

I’ve at times had quirks mode stuff in Comic Snarfer so I don’t blame the webkit devs for the messed up sites. I blame the sites.

@neauoire @ameliedumont :D

@neauoire a drake meme.
drake_no: "modifying your website to work on browser"
drake_yes: "Modifying webkit to work on your website"

@neauoire reading through that file made me really sad :(

@neauoire The `git blame` context is interesting: https://github.com/WebKit/WebKit/commit/fbc716afc0525738d3d92576ad976aa3e6e81cc0

But the meme you chose is on the money. When everyone chases the most users and users want things to "just work", whose blame it is depends on who has the fewest users. If you're big, others mould themselves to you.

The solution: stop being users.

@neauoire You'll like this: there's a _standard_ for browser quirks.

https://quirks.spec.whatwg.org

"What, oh, you thought _you_ could have quirks, plebe?"

@akkartik @neauoire That's WHATWG for you! If a page looks different browser it's broken, so they have to prescribe every tiny little detail of how to render it.

Then they all forget about the novel they wrote to cover *everything* and imitate Chrome instead.

@alcinnz @akkartik @neauoire Novel? It's more like an encyclopedia.

@lanodan @akkartik @neauoire Too true!

I did take a wordcount recently, and it's almost as long as "To Green Ivory Tower", one of the world's longest novels known to Wikipedia.

@alcinnz @akkartik @neauoire Word Count of just HTML/CSS/SVG/… or almost all the relevant W3C+WHATWG documents for browsers? (good luck)

@lanodan @akkartik @neauoire Wordcount of the main WHATWG "living standard", covering HTML, XHTML, & the DOM. I'm not sure whether that includes MathML & SVG.

It includes many of JavaScript's APIs but not JavaScript itself. It doesn't include CSS or HTTP(S).

@drwho @neauoire

That's also a new feature, I think.

@neauoire (this is rhetorical; other comments confirmed my fears.)

@vertigo @neauoire My assumption is that Chrome does something wrong, these sites code for Chrome and WebKit acts more like Chrome for these sites.

@vertigo @neauoire webkit is safari but kinda, yeah, it might break

@charlag @neauoire As I recall, Webkit is also Konquerer (it was originally a KDE library) and is the basis for Google's rendering engine. Am I misremembering?

@vertigo @charlag @neauoire Konqueror had khtml that was forked into WebKit. Chrome then started using WebKit but later forked it into Blink. As for Konqueror, at some point they moved to the Qt Web component which is Blink-based these days, I think.

GNOME-related stuff and Safari use WebKit, Firefox does its own Gecko work, every other "big" HTML consumer is probably based on Blink these days (if not on the entire Chromium browser, like Vivaldi, Brave and Edge).

@patrick @charlag @neauoire Ahh, there's my confusion. I thought WebKit was originally a KDE project.

@somnius @neauoire I'm utterly shocked too!
Legally, it may be seen as unfair advantage and could trigger procedures in some jurisdictions.