this post was submitted on 08 Oct 2024
37 points (95.1% liked)

Firefox

20357 readers
105 users here now

/c/firefox

A place to discuss the news and latest developments on the open-source browser Firefox.

Rules

1. Adhere to the instance rules

2. Be kind to one another

3. Communicate in a civil manner

Reporting

If you would like to bring an issue to the moderators attention, please use the "Create Report" feature on the offending comment or post and it will be reviewed as time allows.

founded 5 years ago
MODERATORS
k_o_t@lemmy.ml
golden_zealot@lemmy.ml
37
What are specific examples of Google shaping web standards, especially ones that require browser support? (lemmy.world)
submitted 9 months ago by TheTwelveYearOld@lemmy.world to c/firefox@lemmy.ml
8 comments fedilink hide all child comments
 

It's no secret that Google has a very large influence. They have influenced web pages into being highly optimized for high search engine rankings, and have pushed AMP: https://www.eff.org/deeplinks/2020/07/googles-amp-canonical-web-and-importance-web-standards-0. However I haven't found any concrete examples of Google pushing web standards that have been adopted and require browser support. I've read comments here and there like this one, that the Shadow DOM was created and pushed by Google, perhaps to make it harder to block ads, but didn't find any sources on that.

you are viewing a single comment's thread
view the rest of the comments
[–] lascapi@jlai.lu 2 points 9 months ago (1 children)

Amazing piece of internet history!! Thank you !

[–] PetteriPano@lemmy.world 6 points 9 months ago

WebRTC isn't necessarily a bad specification.

But that history shows how they draft a specification, implement a service around it at a fast pace (in this case even with a takeover), and many years later the draft turns into a än official specification.

Other browsers have no choice but to fall in line behind the draft if they want to stay relevant. And they did.

IE did the same shit with their marquee-tag back in the day. Last I checked it still works on Firefox. (It's still not in any w3c specification)