The end of the year is around the corner and it’s time to look into the future of Front-end. In this post I will talk about my wishes for 2016 and why I would love to see these three features implemented.
Container queries #
We’re not designing pages, we’re designing systems of components. – Stephen Hay
With media queries for every container our component lives in, we need to specify how to rearrange things in that context. By using container queries we can specify CSS for a component based on the dimensions of the container. This means your components are not dependent on the screen size, but on the container; Fantastic.
Service Worker ships in Safari and Edge #
I am really excited about Service Worker (probably not as excited as Jake Archibald, but still) and can’t wait until Safari and Microsoft Edge will implement Service Worker. I am pretty sure it will come to Edge in 2016, although they still have it listed as Under Consideration at the moment. You should vote for it.
To be honest, I am not so enthusiastic about Safari – Service Worker is on the 5-year plan of WebKit – but even if it will ship to WebKit next year it doesn’t mean it will be shipped in Safari.
Nevertheless, why I really like Service Worker is that it plays along nicely with progressive enhancement, offers not only an offline experience – but improves performance and all the other exciting things you can use it for.
If you want to see Service Worker in every major browser next year the best is to make a lot of noise about it, by using Service Worker today in as many sites as possible and by writing about it again and again.
Parent and previous sibling selector #
Parent selectors and previous sibling selector have been on the wish list of Front-end developers for years. The main points they are not implemented yet is that they are too expensive to implement and that they are pretty inefficient.
While this may still be the case I think now is the time to implement them as an experimental feature and see what developers will make of it and how inefficient it really is. If the performance is not acceptable either some clever browser developers can change that or it will be removed again. If it turns of to be more efficient than expected it can be shipped without using an experimental flag; This would make many developers very happy.
What features do you want to see in browsers in 2016? #