5 ms·
"Website suddenly breaks on browser that is still in beta and likely isn't baked into all of the acceptance tests" seems like a completely expected result. Are
by UncleMeat 8y ago
"Website suddenly breaks on browser that is still in beta and likely isn't baked into all of the acceptance tests" seems like a completely expected result.
Are you suggesting that a new browser that isn't out of beta should be less likely to weirdly break on some websites?
- ChrisSD 8y agoConsidering it uses the same rendering engine as the most popular browser in the world?
- 8ytecoder 8y agoMicrosoft Chrome is essentially Chrome slapped with a new, pardon the pun, chrome. If a website works on Chrome it should work on the MS version as well - assuming they haven't made many breaking changes - and from what I have read so far they have only replaced auxiliary services and haven't altered the rendering engine.
- j_koreth 8y agoPresumably they're still loading a version of the website which Trident/Edgekit which used to make up for the discrepancies between the other browsers.
- kevingadd 8y agoThe Edge devs went out of their way to craft a useragent that doesn't trigger Edge UA sniffing, which is why the pages used to work until Google intentionally broke them in Edge.
- hackily 8y agoDo you have any sources that talk about these breaking issues? I wouldn't be entirely shocked that Google would be doing this, but I do want to see more than just one anecdote that it's ill intent rather than incompetence.
- partiallypro 8y agoExcept if you change the user agent it works.
- spankalee 8y agoWhich easily explains the warning that was shown on docs. A misparsing of a new, never-before-seen user-agent string (especially one with an apparent typo) could lead the code to assume that the browser is indeed an older, no longer supported version.
- deleted 8y ago[deleted]