5 ms·
> ... weird chromium only behaviors that websites rely on these days to do things (and egregiously so if they detect an agent remotely resembling chrome). This
by gjvc 5y ago
> ... weird chromium only behaviors that websites rely on these days to do things (and egregiously so if they detect an agent remotely resembling chrome).
This sounds like the IE6 disaster all over again.
- peakaboo 5y agoPlenty of people said this would happen when chrome started dominating, but since people refused to switch browsers, here we are.
- gjvc 5y agothis guy said it best https://www.youtube.com/watch?v=aYT2se94eU0&t=1414s https://www.youtube.com/watch?v=aYT2se94eU0&t=1414s
- parhamn 5y agooh man. I need to find some time to write about how bad it is. The gnarliness spans the whole stack. From weird java-applet like API escalation behavior if chrome is detected (e.g. Google properties feature gate a ton around this) to how there is not even a clear way to get a DRM license for a custom browser without waiting for Google indefinitely [1]. Here's a challenge: fire up a chromium fork and get it to run a relaxed DRM website like Netflix. If you get that far now try loading HBOMax with their fingerprinting/DRM protection on top. I'm not even sure it'd be possible in FF (at least without some DRM piggy backing if there isn't one). [1] https://blog.samuelmaddock.com/posts/google-widevine-blocked-my-browser/ https://blog.samuelmaddock.com/posts/google-widevine-blocked...
- piva00 5y agoYup, as someone who worked on fixing issues with IE5/IE6/IE7 behaviours I definitely feel the slow burning fire of Chrome repeating that whole saga once again. And probably in a much more painful way given the explosive growth of the internet and browsers since the early 2000s (I started working with web dev around 2005).