Today we'll have a short look at what (we hope) 2013 will bring us — browser-wise, that is. This is by no means a reliable prediction, and may in some cases be plain old wishful thinking. Nevertheless, we want to make a short list of neat things that may or may not come to the web the coming year(s).
More layout options
Internet Explorer already debuted grid layout, flexbox is coming along nicely (the new spec, that is), and we might even get a glimpse of template layout. Anyway, grid-layout is quite powerful; read the 24Ways article Giving Content Priority with CSS3 Grid Layout by Rachel Adams for a more in-depth look at this.
So maybe in 2013 we may finally be able to build most layouts, including content-priority without having to resort to a bunch of wrapper divs and dirty float hacks. We're sure that both we, our designers, and our clients would be happier for it.
Doing more with the flow
We've demonstrated some parts of exclusions and regions, but these are merely the tip of the iceberg. Especially exclusions is pretty damn high on the most wanted list. We have long wanted to have content flow in or around arbitrary shapes, and exclusions will allow you to do that. Go and have a look at Ryan Stewart's Experimenting with CSS Exclusions, and be amazed.
Blending your images
How many times have you encountered a blend-mode in a file from your designer that wasn't set to normal, but to "screen" or "multiply"? We have, more than once. And quite frankly, we were just as dissapointed as the designer when we have to send it back to get it "fixed". The functionality described in the Compositing and Blending Level 1 spec would allow us to do this without too much fuss. Adobe even has an experimental Webkit fork with the spec implemented. Find out more about compositing and blending on the Adobe Web Platform Team Blog.
CSS Selectors Level 4
Work on the CSS Level 4 has started quite some time ago, and we may see some of the specs seep into browsers somewhere next year. The most
exiting selector will be the subject selector, with which we can select to which part of the css selectors our CSS should apply:
li:only-child would style any
ul that only has one
li. Read the Selectors Level 4 spec to see all the awesomeness in progress!
Moar device API's
In this year's HTML & CSS Advent we've seen quite some device APIs:
getUserMedia for webcam and microphone, the Device Orientation API for
accessing the gyroscope/accelerometer, and the Battery API to get battery readings. And then there was the Geo Location API. We expect to get
access to more and more device APIs. An example of this is the Vibration API, which gets you access to a device's vibrator. David Walsh
already put out an extensive blogpost about the Vibration API.