5 ms·
Finally! Before anyone starts moaning about incompatibility, let's face it: developers start to rely on new features the moment they're added. Differentiating
by TazeTSchnitzel 14y ago
Finally!
Before anyone starts moaning about incompatibility, let's face it: developers start to rely on new features the moment they're added. Differentiating between different implementations is pointless, since CSS's design means you can specify a property multiple times and your browser will only use the one it understands. The current system also excluded other rendering engines who web developers didn't consider.
So this is a huge win for us, the developers.
- ellyagg 14y ago"Let's face it: developers start to rely on new features the moment they're added." "So this is a huge win for us, the developers." There's a contradiction here, and I'm not being cute. Your argument is not the only argument to be made, and personally, as a developer, I preferred the old way. Yep, there are negative externalities, and that always has to be weighed, but I think it was a reasonable approach to allow developers to weigh the use of cutting edge features against their own communities, needs, and goals. That calculation would change depending on how many browsers were offering a proposed recommendation and the browser proportions of your viewers. Lots of interesting stuff was posted around the web, including here, taking advantage of these things. On the other hand, there's virtually no community for whom it would be reasonable to ask to make config changes to view a site, so you you simply can't use cutting edge features. Experimental site designs will be harder to show off and we'll have less public consideration of the implications of new recommendations since there's much less joy in putting together projects that few people will see.
- TazeTSchnitzel 14y ago>On the other hand, there's virtually no community for whom it would be reasonable to ask to make config changes to view a site Actually, HN is exactly the sort of place where people might be willing to do so. Things are posted here which require specific browsers or about:flags changes in Chrome, what would change?
- dragonwriter 14y ago> On the other hand, there's virtually no community for whom it would be reasonable to ask to make config changes to view a site, so you you simply can't use cutting edge features. Experimental site designs will be harder to show off and we'll have less public consideration of the implications of new recommendations since there's much less joy in putting together projects that few people will see. Showing off demos leveraging experimental browser features that don't happen to be CSS features has often been done with requests to make config changes, because the "put it behind a config flag until it is ready" is pretty standard for everything other than CSS (and, actually, browser vendors have also done it for plenty of experimental implementations of CSS, whether or not the features themselves are standard or vendor-prefixed experimental extensions.)
- tomelders 14y agoSo what happens when someone introduces a new whiz bang css feature that Chrome handles badly? Something you might, as a developer, want to disable in Chrome, but leave in for everything else? Or any other browser since they're all prone to introducing flakey implementations of CSS sometimes. All this means is we'll have to go back to the old ways of sniffing out browsers, and I fail to see how that's better. Nor do I look forward to a deluge of websites prompting me to fiddle with a config to "get the full experience". Most web developers have very little sway when marketing or clients demand certain things, and this is likely to be something they demand.
- TazeTSchnitzel 14y ago>So what happens when someone introduces a new whiz bang css feature that Chrome handles badly? Something you might, as a developer, want to disable in Chrome, but leave in for everything else? Or any other browser since they're all prone to introducing flakey implementations of CSS sometimes. >All this means is we'll have to go back to the old ways of sniffing out browsers, and I fail to see how that's better. The situation is no different just now, because -webkit- applies to Safari, Opera and many mobile browsers, not just Chrome. :/ >Nor do I look forward to a deluge of websites prompting me to fiddle with a config to "get the full experience". Most web developers have very little sway when marketing or clients demand certain things, and this is likely to be something they demand. "Use a modern browser [actually, Chrome] to get the full experience" is not an uncommon sight these days.
- tomelders 14y agoI was being polite. I'm talking about IE specifically. >"Use a modern browser [actually, Chrome] to get the full experience" is not an uncommon sight these days. Yup, and it's sucky. It's no different to "this site is optimised for Internet Explorer".
- TazeTSchnitzel 14y ago>I was being polite. I'm talking about IE specifically. Well, this won't help you here anyway. By the sounds of things, features won't be enabled by default until they're ready. Things currently aren't unprefixed until they're ready. The only way to avoid IE if the feature is unprefixed is UA sniffing. No change. >Yup, and it's sucky. It's no different to "this site is optimised for Internet Explorer". It's quite different, actually. Chrome is just quick at implementing web standards, they aren't dictating things and people aren't relying on proprietary APIs.
- zmmmmm 14y agoHmm, isn't it true though, for example, that without that we'd have had to wait a long time to get simple things like border-radius that were supported in all the browsers but hidden behind vendor extensions? Having experimental features available to developers creates pressure for all browsers to move forward. Without that we won't know what is important to developers because they'll be stuck using what the browser maker's deign to make "official". Just playing devil's advocate here ...
- TazeTSchnitzel 14y agoWell, hopefully things might get through quicker. But that is indeed a problem.
- jayflux 14y agoYes exactly. The 'yay no vendor prefixes!' crew seem to have very short memories on what it was like before vendor prefixes..IE Waiting a LONG time (years) for a CSS feature to be 'recommended' by the w3c. Vendor Prefixes were the best of a bad situation, I think they will be missed quite quickly. I'm all up for this movement, but the W3C will need to move a lot quicker if this is to happen. Otherwise innovation will just grind to a halt again like it did before.