4 ms·
Note, this is a sarcastic opening to a serious proposal — that Google not dump elements into the WHATWG HTML spec without user discussion and use cases: Th
by Terretta 7y ago
Note, this is a sarcastic opening to a serious proposal — that Google not dump elements into the WHATWG HTML spec without user discussion and use cases:
The way Google has gone about this seems to be…
1. Ooh! I have a cool idea!
2. Other people in Google agree with me!
3. Other Google projects could benefit from this?
4. Let's stick it in Chrome!
5. Oh, guess we should tell the community what we're doing.
He thinks maybe <toast> is fine (pattern of a notification container showing up and disappearing again makes sense), but concerned how it’s been introduced.
- tannhaeuser 7y agoI don't see how toast is different from the countless proposals for new declarative UI HTML elements that have been submitted over the years, and ignored or withdrawn (such as menu/menuitem), other than it coming from Google (and maybe Google not wanting to expose that functionality via a JavaScript API?) The reasoning against new UI elements has always been the same - they're inessential when JavaScript is needed anyway. I think this incident should make it very clear to everyone that HTML as seen by "browser vendors" (Google) is a very different thing from HTML the markup language as used all over the world for personal, business, medical, legal, and cultural documents, and which demands community representation and participation.
- geocar 7y ago> I don't see how toast is different from the countless proposals for new declarative UI HTML elements that have been submitted over the years The difference is that if Google introduces a new tag and starts using it, then every other vendor must implement the tag, or the [potentially popular] applications that use it [made by Google] will simply not work. That's not a power that "countless proposals for new declarative UI HTML elements" have. > I think this incident should make it very clear to everyone that HTML as seen by "browser vendors" (Google) is a very different thing from HTML the markup language as used all over the world for personal, business, medical, legal, and cultural documents, and which demands community representation and participation. Google is not a browser vendor; they do not sell web browsers. Google sell advertising, and it's absolutely critical to Google's future to get everyone on the only web browser that has crippled ad blocking and privacy capabilities.
- scarface74 7y agoIf Google implements something an Apple doesn’t on the iPhone then what?
- jakelazaroff 7y agoiOS has less than 15% market share globally. https://www.idc.com/promo/smartphone-market-share/os https://www.idc.com/promo/smartphone-market-share/os
- scarface74 7y agoThat’s a nice and (irrelevant) statistic. No one targets a “global” audience with a website. If I’m targeting North America, Europe, or Japan, why do I care that a billion people in India use Android phones? Even in countries where iOS is a sliver of the overall population like China and India, if you want to reach the affluent population, you still need to target iOS users. How fast do you think someone creating a website in the US will get fired if they said they are going to ignore iOS users because iOS is only 15% of the global market? If iOS didn’t matter do you think Google would be paying Apple a reported $9 billion a year to be the default search engine?
- jakelazaroff 7y agoNorth America is about the only significant market where iOS has a ton of market share, and the world is not North America. If you're targeting Europe, iOS has only 25% [1]. Not sure why you said Japan instead of Asia, but iOS market share there is less than 15%; even worse than it is worldwide [2]. People don't have their browser choices etched in stone, and Google's services are a powerful form of persuasion. If they work in Chrome but not other browsers, people will just switch to Chrome. It's not 2009 anymore. iOS simply doesn't give Apple the power to stop Google here. [1] http://gs.statcounter.com/os-market-share/mobile/europe http://gs.statcounter.com/os-market-share/mobile/europe [2] http://gs.statcounter.com/os-market-share/mobile/asia http://gs.statcounter.com/os-market-share/mobile/asia
- inflatableDodo 7y ago>"He thinks maybe <toast> is fine (pattern of a notification container showing up and disappearing again makes sense), but concerned how it’s been introduced." They really should have resurrected the blink tag and added a property for the number of iterations required.