Microsoft and Google, sitting in a tree, working on browser compatibility
- Reference: 1616508373
- News link: https://www.theregister.co.uk/2021/03/23/compat2021/
- Source link:
Those who remember Microsoft's [3]shenanigans during the heyday of Internet Explorer will doubtless be feeling a twinge of irony at the thought of the Windows giant signing up to a browser compatibility initiative, but here we are.
[4]
Google is very much the gorilla in the room when it comes to browsers nowadays and the Chromium project that underlies its Chrome browser forms the basis of many popular web-surfing applications, including Microsoft's Edge and Vivaldi. The ad slinger's involvement in the [5]Compat 2021 project augers well for progress.
"Compatibility on the web has always been a big challenge for developers," [6]said Google with breath-taking understatement, before noting research directing the efforts of engineers to five main pain areas, all of which fall under CSS (rather than, oh, maybe browser extensions?).
[7]
Vivaldi opens up an exciting new front in the browser wars, seeks to get around blocking with cunning code [8]READ MORE
Engineers at Microsoft, Google, and Igalia (regular contributors to Chromium and WebKit) will be working on fixing five areas in 2021 – CSS Flexbox; CSS Grid; transforms; the aspect-ratio property; and position: sticky.
Progress can be measured on a handy dashboard, showing how well preview builds of Chrome/Edge, Firefox, and Safari are doing against those focus areas, with up to 20 points per feature assigned to the score for a potential total of 100.
The goal of browser compatibility across vendors is noble, certainly for developers weary of the vagaries of CSS when dealing with Chromium, Gecko, or WebKit-based browsers.
However, while focusing on five problematic areas is welcome, the initiative does not address other issues that might leave customers wondering just how compatible their chosen browser is, namely the habit some vendors have of [9]blocking website functionality based on what is lurking in the User Agent string .
[10]
If browsers do indeed become as compatible as Google, Microsoft, and the Compat 2021 initiative desire, then such shenanigans will not be needed. Right? ®
Get our [11]Tech Resources
[1] https://www.theregister.com/2021/03/17/google_ftc_saga/
[2] https://blogs.windows.com/msedgedev/2021/03/22/better-compatibility-compat2021/
[3] https://www.theregister.com/2000/04/04/judge_finds_against_ms/
[4] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/applications&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=2&c=2YFoeqRisDlmbmjDIiCWr0QAAAMk&t=ct%3Dns%26unitnum%3D2%26raptor%3Dcondor%26pos%3Dtop%26test%3D0
[5] https://wpt.fyi/compat2021?feature=summary
[6] https://web.dev/compat2021/
[7] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/applications&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=3&c=33YFoeqRisDlmbmjDIiCWr0QAAAMk&t=ct%3Dns%26unitnum%3D3%26raptor%3Deagle%26pos%3Dmid%26test%3D0
[8] https://www.theregister.com/2019/12/19/vivaldi_user_agent/
[9] https://www.theregister.com/2019/12/19/vivaldi_user_agent/
[10] https://pubads.g.doubleclick.net/gampad/jump?co=1&iu=/6978/reg_software/applications&sz=300x50%7C300x100%7C300x250%7C300x251%7C300x252%7C300x600%7C300x601&tile=4&c=44YFoeqRisDlmbmjDIiCWr0QAAAMk&t=ct%3Dns%26unitnum%3D4%26raptor%3Dfalcon%26pos%3Dmid%26test%3D0
[11] https://whitepapers.theregister.com/
Re: Wow...
They'll get bored, hipsters always do
Re: Wow...
You forgot to add that they will totally ignore all that lovely code that tracks and snoops on the users.
Google would not know what to do without all that lovely data that just happens to fall right into their laps.
Cynical? You bet.
Been there, done that, ...
... here is the [1]T-shirt .
[1] https://www.amazon.co.uk/Web-Developer-Office-Gift-T-Shirt/dp/B07G8NWMNF
Weird way round?
I thought the web had documented standards that browser developers were expected to follow. It appears I was wrong. It seems that browser developers are creating the standards the web finds itself obliged to follow. What's worse, different browser developers are tinkering with the standards in competition with each other. This attempt at "compatibility" merely highlights (and maybe attempts to partially rectify) the problem they've created in the first place.
None of this is really for us the users - it's "competition".
Re: Weird way round?
The annoying thing about standards is that they're written by humans. That means that at some level there is ambiguity. If different vendors produce software to different interpretations of the standards, but both 'correct', that's not entirely their fault.
Working together to reach a common understanding of how to interpret the standard (ie resolve the ambiguity) is A Good Thing.
Then there are the extensions which are useful but bleeding-edge, which they want to try out before codifying a standard for. Work out the bugs, document it, then get others to adopt it. It might not be the ideal workflow, but I can't see how you can get around that without stifling innovation.
As someone who's been building websites for 20+ years, I can tell you that things are a hell of a lot better now than they ever were before!
Wow...
...what a clever idea. Fixing stuff rather than adding more bloat no one wants.