4 ms·
I don’t like how Google now gets to ‘launch new HTML elements’ as they see fit for their own purposes.
by tinus_hn 8y ago
I don’t like how Google now gets to ‘launch new HTML elements’ as they see fit for their own purposes.
- neilalexander 8y agoAt the end of the day, web standards are nothing more than advisory and Google own a clear majority of browser market share. Who is going to stop them?
- molf 8y agoWe are, by using and recommending browsers not owned by advertising conglomerates.
- neilalexander 8y agoI'm a very happy Safari user but evangelism is only going to get you so far. There need to be better alternatives.
- pellefant 8y ago> Who is going to stop them? We are, 10s of millions of users (if not 100s).
- oarsinsync 8y agoIf mobile app store revenues can be used as a metric for revenues on the web generally, iOS users are a valuable demographic to target, even if they are the minority. If your website doesn't work in Safari, you're going to lose revenue. <portal> doesn't feel like something that will ever be supported in Safari.
- jadell 8y agoPeople used to say that about IE6, before Firefox and Chrome came along.
- int_19h 8y agoIE6 lost that battle because it stagnated - it wasn't just not keeping up with new standards, it wasn't innovating in general. We don't know if it turned out the way it did, if Microsoft kept proactively extending HTML in new IE versions. But given that this is largely what was happening in the IE/NN mortal combat era that preceded IE dominance, I'd expect "this browser best works in ..." to make a comeback. And, indeed, it's increasingly common to see websites explicitly say that they want Chrome. Especially new Google projects...
- libria 8y agoIt's not up to Google, it's up to web developers. If they find <portal> useful they'll implement it which forces FF/Safari to create their own implementations. Dart ran natively in Chrome once. Why doesn't it now? Because webdevs didn't care enough to write native Dart on the front-end.
- paulirwin 8y ago> as they see fit They're doing this in the open through the W3C WICG process [1]. They're not doing this as they see fit. > for their own purposes. Open standards are available for anyone to use and benefit from. That they may have had a use case in mind when defining the spec does not invalidate it; rather, it reinforces it and shows its value. 1: https://wicg.github.io/portals/ https://wicg.github.io/portals/
- jmull 8y ago> They're doing this in the open through the W3C WICG process [1]. They're not doing this as they see fit. I really don't see a significant difference. They can pretty much propose whatever they see fit through WICG and implement it in Chrome as they see fit. By the way, this isn't a standard by any reasonable definition of the word.
- joshuamorton 8y agoThat's how modern web standards are done. If people like it, other browsers will adopt it and then the standard will too. If people don't, they won't. But every browser runs nonstandard features as part of experiments to implement new things. One way of looking at it is that the standardization process is "propose and implement whatever you want, but it doesn't become a standard until another browser implements it and consensus is achieved". This is a direct response to the problems of the W3Cs old way of defining large, pie in the sky, standards without any implementation, and then only much later realizing that they were bad.
- eterm 8y agoNo, given chrome's market share other browsers are forced to implement it or people will consider those browsers broken. Google are now where microsoft were when they launched IE6, adding features as they see pleased to support their own products and revenue. Back then the web population was savvy and not so reliant on microsoft that they could jump to firebird/firefox/opera when things got really bad. The modern web users don't have that option because google are far more dominant now than microsoft ever was. Back then people would joke about their grandma being "stuck" on IE6, but that's the level of technical aptutide of the whole web now. Just ordinary people wanting to get on with their own business. Back in '02 chances are you'd be re-install XP all the time and during one of those installs a technician could install firefox (or later chrome) and you'd be set up. That doesn't happen now, OSes "just work" and people aren't changing their browser.
- jccalhoun 8y agoembrace and extend...
- ENGNR 8y agoIt’s behind a feature flag, they’ve done it the correct way