6 ms·
The good news is no -blink prefixes! Blink, like Mozilla, will avoid shipping vendor-prefixed features: Historically, browsers have relied on vendor prefixes
by cpeterso 14y ago
The good news is no -blink prefixes! Blink, like Mozilla, will avoid shipping vendor-prefixed features:
Historically, browsers have relied on vendor prefixes (e.g., -webkit-feature) to
ship experimental features to web developers. This approach can be harmful to
compatibility because web content comes to rely upon these vendor-prefixed
names. Going forward ... we will instead keep the (unprefixed) feature behind
the “enable experimental web platform features” flag in about:flags until the
feature is ready to be enabled by default.
- mikewest 14y agoYes! Prefixes are damaging. We're hiding things behind flags instead, which gives savvy developers the chance to experiment without the risk that sites will begin to depend on those experiments.
- kmfrk 14y agoI, for one, can't wait to cut 20% of the code in my stylesheets.
- kaolinite 14y agoIn the meantime, you can use LESS mixins to reduce duplication. This library is pretty handy: http://lesselements.com/ http://lesselements.com/
- robryan 14y agoThe parent was likely referring to them being in the stylesheet at all, rather than the way they are managed. Any stylesheet compiler is still going to have the vendor prefixes in the compiled stylesheet.
- plorkyeran 14y agoIn practice you won't actually be able to drop them from the compiled stylesheet for a very long time, of course.
- Achshar 14y agoChrome has a very quick release cycle, so I don't see why not?
- TazeTSchnitzel 14y agoFinally! 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.)
- MatthewPhillips 14y agoSince every developer will want it to work in Chrome, this effectively kills vendor prefixes once and for all. It doesn't make sense for Microsoft or WebKit to continue to include them.
- fpgeek 14y agoI wonder if that's where the name came from: something any decent web developer would be ashamed to put in a vendor prefix.
- tuananh 14y agothey probably mean how fast it would render the page.
- WiseWeasel 14y agoSo the user would have to enable experimental flags (which will happen approximately never) to see advanced features? And that's supposed to be good for developers? So things like -webkit-box-reflect will no longer be supported in Chrome?
- workbench 14y agoThat sounds far worse to me, so I can't even use the new features as they arrive. I couldn't care less if they add -blink, it takes minutes to push that through a modern CSS codebase. At least I can use the features where they exist.
- klapinat0r 14y agoSorry if I'm dense, but unlike mozilla? are mozilla css extensions not "prefixes" in this context? https://developer.mozilla.org/en-US/docs/CSS/CSS_Reference/Mozilla_Extensions?redirectlocale=en-US&redirectslug=CSS_Reference%2FMozilla_Extensions https://developer.mozilla.org/en-US/docs/CSS/CSS_Reference/M... or can someone explain to me the difference?