undefined | Better HN

0 pointsUncleMeat6y ago0 comments

"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?

0 comments

8ytecoder6y ago

Microsoft 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_koreth6y ago

Presumably they're still loading a version of the website which Trident/Edgekit which used to make up for the discrepancies between the other browsers.

kevingadd6y ago

The 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.

1 more reply

partiallypro6y ago

Except if you change the user agent it works.

spankalee6y ago

Which 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.

ChrisSD6y ago

Considering it uses the same rendering engine as the most popular browser in the world?

j / k navigate · click thread line to collapse