Skip to main content

Flags vs Vendor Prefixes for Experimental CSS

Google recently announced that it will be switching Chrome's rendering engine to a fork of Webkit, called “Blink”. If you're interested, you can read their blog post about Blink.

One of the changes we will be seeing in Blink, is the use of browser flags in place of vendor prefixes.

What this means, is that rather than prefixing experimental CSS with -webkit-, -moz-, -ms-, -o-, -khtml-, etc.; We will be required to enable these attributes using a flag in the browser (like the ones currently at chrome://flags).

If you ask me, both ways have their advantages and disadvantages. Though, in the end, I lean towards the flags over the vendor prefixes, and here's why:

#1 Code Bloat

On average, using CSS with vendor prefixes requires writing it 5 times. Every time you use it.

#2 Future Friendly

Eventually, prefixed code will be replaced by the unprefixed code.

#3 Browser Dev Friendly

Browsers tend to continue to support the prefixed code, even if it doesn't make it to the spec or gets changed. If they didn't, they could break existing sites that relied on this code. This compounds and grows as more experimental features are added, which adds overhead to the browsers and more work for browser devs.

Conclusion

By moving support for experimental (spec not yet approved) CSS into an optional flag in the browser, and supporting only a single version of the code, we may lose the opportunity to expose these features to the masses early, but we gain a much more stable and maintainable environment.

Comments

Post a Comment

Popular posts from this blog

Element.focus() in IE9 running Jasmine tests with Karma

I recently udpated our Jasmine unit tests to run in Karma ; expanding our browser coverage, adding code coverage reports , and using fixtures for testing DOM manipulation . One of my tests kept failing in IE9, but only when I ran from the console. If I attempted to debug in the browser, everything passed. It turns out that IE9 (at least) needed a few ms to catch it's breath before correctly focusing on the starting element. To do this, I just added a 100ms delay before each test ran (Using Jasmine 2.3). beforeEach(function(done){ loadFixtures('myfixture.html'); // Setting focus in IE requires a delay to work correctly! setTimeout(function(){ done(); }, 100); });
Post a Comment
Read more

Get width and height of a remote image with VB .NET

The Problem I wanted to grab the width and height of an image that was on a remote server. I've done this with PHP, but never in .NET. The Solution I did a little digging and came across this code (slightly modified for my own purposes). Dim request As HttpWebRequest = DirectCast(WebRequest.Create(URL), HttpWebRequest) request.Method = "GET" request.Accept = "image/*" Dim response As HttpWebResponse = DirectCast(request.GetResponse(), HttpWebResponse) Dim s As Stream = response.GetResponseStream() Dim bmp As New Bitmap(s) Width = bmp.Width Height = bmp.Height
Post a Comment
Read more