That's new "you have made it when"...they need to change the browser engine for your website.
WebKit Quirks
31–40 of 91 posts
Re: WebKit Quirks
#32shouldBypassBackForwardCache() // Google Docs used to bypass the back/forward cache by serving "Cache-Control: no-store" over HTTPS. // We started caching such content in r250437 but the Google Docs index page unfortunately is not currently compatible // because it puts an overlay (with class "docs-homescreen-freeze-el-full") over the page when navigating away and fails // to remove it when coming back from the back/…
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?
Re: WebKit Quirks
#33Domain name specific quirks? What in the world...
How do these domain-specific quirks get into WebKit? Is it advocated by the companies? By the users? By the devs?
I'm just curious how these changes actually make it to millions of people's browsers
Re: WebKit Quirks
#34Earlier quoted context omitted.
Why shouldn't it show it in the same state? Seems like a reasonable thing to do.
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…
No, it's just one of too many things, big and small, making browser web apps annoying. The entire point of a browser was a relatively simple viewer app that renders docs ok on most devices; not an opionated renderLikeChrome mode. If the basic concept of leaving a page for linked content, then coming back can't be handled without heuristics, then clearly the web app model is broken af.
Re: WebKit Quirks
#35Anyone who's read a few Old New Thing posts would know that Windows must be full of similar checks.
IIRC, the “checking for a solution to the problem” dialogs were added because they (Microsoft) would submit an actual bug report to the developers, and if they offered a solution, Microsoft’s servers would respond with it. I’ve never seen it work, but IIRC, they added it back in the Windows 95 days (when there was a lot less software to deal with).
They really need to get rid of this.
Re: WebKit Quirks
#36shouldBypassBackForwardCache() // Google Docs used to bypass the back/forward cache by serving "Cache-Control: no-store" over HTTPS. // We started caching such content in r250437 but the Google Docs index page unfortunately is not currently compatible // because it puts an overlay (with class "docs-homescreen-freeze-el-full") over the page when navigating away and fails // to remove it when coming back from the back/…
I'm actually having a similar issue with my web app currently and I'm not sure what the best way to solve it would be. I was thinking of setting a checkbox in an invisible form when the page loads initially, and force a real reload if the checkbox was previously set, but that seems like a terrible hack. Any ideas?
Re: WebKit Quirks
#37Domain name specific quirks? What in the world...
This isn't new, I remember Opera (versions 12 and older) used to come with a privileged .js file that would apply patches to websites. It was used mostly to fix those that blocked Opera when they detected its user agent or popular websites that ran code using proprietary functions or css properties (things that only Chrome or Internet Explorer implemented but weren't part of the standard).
Re: WebKit Quirks
#38There was a viral tongue-in-cheek tweet this month "how to prevent scrolling in Safari when..."?
1. Buy Zillow. Destroy the company.
2. Redirect your website to zillow.com
(it was more fun that what I wrote)
https://github.com/WebKit/WebKit/blob/f43587ec2416b86eecef50...
Re: WebKit Quirks
#39Earlier quoted context omitted.
> At the end of the day, this is the only way that non-Chrome browsers can meet Google’s hegemony Except these quirks include a whole lot more than just Google. Some of the domains in there: 1. nytimes 2. twitter 3. ralphlauren 4. baidu 5. warbyparker 6. nfl 7. gizmodo 8. microsoft I'm not sure what each different piece of code does but there is many more domains in there.
By Google’s hegemony, I was talking about developers only testing in Google-developed rendering engines, not their web properties.
Aah! Pardon me. That makes more sense.
Re: WebKit Quirks
#40It's like that saying about debt.
When a browser renders your 500 mau site badly it's your problem.
When a browser renders your 50,000,000 mau site badly it's the browser's problem.