Google has announced plans to implement some new HTML elements and is inviting comment on the best ways to do this, however it has violated even its own process by not consulting before announcing its plan to implement.
There’s an interesting discussion on how to implement new elements, but this topic is not about that. It is to highlight another way in which Google is using its monopoly control of the web via is Chrome browser to take ownership of the web itself.
Details here:
toast.md
# Are Web Standards Toast?
I find myself in a tempest in a toaster. Yesterday I (and much of the web standards world) learned about two possible new HTML elements proposed by Google, `std-toast` and `std-switch`. I had no idea what “toast” meant in the context of the web, a problem shared my many other people. It turns out it’s a UI pattern, those little notices that pop up and then disappear without user interaction.
But wow, new HTML elements! This is the holy grail. In my part of the web we don’t even dream about new HTML elements. Oh, we’ve tried, but Hixie didn’t much care for `footnote`, WICG didn’t much care for list titles, and no one much cared about `author`. Just last week the author of the extensible web manifesto warned me to never expect new HTML elements, due to the difficulty of changing the parser.
But my concern wasn’t so much about the nature of the new elements, but of how we learned about them and what that says about how web standardization works. My [first tweet](https://twitter.com/dauwhe/status/1138811060981575680) about this yesterday sums up my initial reaction:
> <std-toast> and <std-switch> feel like a new approach to standardization, as does requesting TAG review on the same day you post an intent to implement.
show original
https://twitter.com/safepress/status/1139521565807325186?s=20
5 Likes
folaht
June 28, 2019, 9:05am
5
torri:
So the web is now toast?
The toast.