That's new "you have made it when"...they need to change the browser engine for your website.
I was surprised to see they're almost exclusively anglosphere websites, i would have guessed a broader variation
WebKit Quirks
61–70 of 91 posts
Re: WebKit Quirks
#62Earlier quoted context omitted.
Yes, it is a real shame, but then again, a lot of these sites are made by reasonably big companies. I'm sure trello and such could fix whatever these input quirks are. Then there's autoplay specific behaviour on facebook, twitter and netflix. Is this really a google hegemony thing, or is this leniency that other sites don't get? I'm just trying to see if there's similar examples in Blink & Gecko right now.
> if (host == "trailers.apple.com") > return true; Even Apple themselves are not immune.
And icloud.com: https://github.com/WebKit/WebKit/blob/21c441ed8ddc83f3e24ad5...
Re: WebKit Quirks
#63That's new "you have made it when"...they need to change the browser engine for your website.
I was surprised to see they're almost exclusively anglosphere websites, i would have guessed a broader variation
The web is surprisingly segregated. Seems there is at least three versions of everything (from my perspective), from websites like the typical social network to utilities people use day to day, english/spanish/chinese.
Re: WebKit Quirks
#64Earlier quoted context omitted.
What makes it broken, out of curiosity? Is there a spec anywhere that suggests that behavior is incorrect? Or is it just because it's not what Chrome does?
Yeah, I'm interested too. I might be wrong, but AFAIK there aren't any specs on how a browser should implement forward/back buttons, right? I'm personally getting a ton of mileage on the Safari's much more stable forward/back cache, the fact that you can go back reliably gives me more comfort than other browsers where going back usually refreshes the page (although I can't really explain how this is much better). I p…
There's a metabug on HTML at https://github.com/whatwg/html/issues/5880 about defining how various platform-exposed features behave in the face of a bfcache (backwards/forwards cache).
Re: WebKit Quirks
#65> domain.endsWith("hulu.com") Huh, does that mean it would also apply on "thisisnothulu.com"? Most other endsWith calls seem to do e.g. `domain.endsWith(".hulu.com")` to only match subdomains.
[deleted]
Re: WebKit Quirks
#66Web UI "standards" are a friggen mess. We really need to rethink it all. For one, if we had a standard state-ful GUI markup language, we wouldn't need to reinvent so many common GUI widgets and idioms using bloated libraries based on JS + DOM.
Second, if web standards allowed true absolute positioning of vectors (as an option), then the layout engines could reside on servers, allowing us to choose a layout engine that best fits domain and need.
Note that while existing web standards do have some coordinate based features, they are too inconsistent to reply upon. If they were any good, we wouldn't need PDF viewers.
Re: WebKit Quirks
#67Domain name specific quirks? What in the world...
Oh, WebKit are absolutely not the only people doing this. Opera used to with their Presto engine, and I’m pretty sure I’ve seen a similar list in Gecko, though I can’t find it now. At the end of the day, this is the only way that non-Chrome browsers can meet Google’s hegemony, unless they give up and adopt Chromium itself. The opportunity cost of switching is too low for browser manufacturers no to have these workaro…
> Oh, WebKit are absolutely not the only people doing this. Opera used to with their Presto engine, and I’m pretty sure I’ve seen a similar list in Gecko, though I can’t find it now.
This is the last (shipped) Presto one for desktop:
https://web.archive.org/web/20190204112249if_/https://github...
Perhaps more surprisingly, this continued into Chromium-based Opera (though archive.org seems not to have that, but that's the OPRdesktop directory in that repo); this was primarily down to sites with a UA string allowlist, and having to lie to get in. (Chromium-based Edge also has a means to override the UA string.)
Re: WebKit Quirks
#68It's fun (and a little depressing) to look at this list, but it exists is basically every popular project. Unfortunately, the incentives are set up for this to essentially be necessary: if something popular doesn't work in your software, users are going to think your code is the one who is broken, not the thing they are trying to use. So you have a sort of a "tragedy of the commons" where if you keep a principled position a user is going to switch to your competitor that supports quirks to get the thing to work.
Re: WebKit Quirks
#69Earlier quoted context omitted.
If it was a static page, then sure. But for dynamic pages or SPAs it more often than not leads to going back to a page in a broken state. Other browsers have better heuristics for when this cache is used. So Safari's behavior is unexpected, even so that the big guys are taken by surprise it seems. I don't really mind either way, the main thing is that it's inconsistent. It's not a huge deal, but it's just one of many…
Conceptually I'd say that clicking a link and then clicking Back should be the same as right-clicking the link and opening it in a new window, and then closing that window. But it wouldn't surprise me if "web apps" makes this hard for some reason.
In my mind the forward back buttons apply to the URL. So you are going back and forward in URL history, as if you were typing the URL in fresh each time. In the old days the back forward buttons were right there next to the URL on the toolbar.
It just occurred to me that on mobile, the back button is not associated with the URL at all, so its not surprising that people don't associate it with that anymore.
I think safari desktop hides the URL as well.
Re: WebKit Quirks
#70Anyone who's read a few Old New Thing posts would know that Windows must be full of similar checks.
Windows has tens of thousands of them. However, the vast majority of them unlike this quirks file are very very specifically gated to an explicit version range, file name, product name, etc etc, typically with consent of the app manufacturer.