Ever since CSS filter effects landed in WebKit, I thought about theirs practical implementation. How will they fit with the current web design trends? At this time, my initial impressions are that the best way to showcase the power of CSS filters is something like an image gallery.
With so many CSS filters to choose from, it will be fun to create image galleries in the future. Further in this article we’ll create a simple image gallery using CSS filters and the CSS3
Whilst at the beginning we had just WebKit nightlies support, now you can view the filter effects using Chrome Canary too. I encourage you to download it in order to view the CSS filter effects in action. Also, I’m pretty sure that soon we’ll see filters support also in stable Chrome’s releases.
Here are the current filter effects:
drop-shadow. Read more about them here.
In this article we’ll be using just the
grayscale effects in order to create our small gallery. Also, the CSS3
:not selector will help us here as you’ll see below.
Getting back to our image gallery, let’s see how the markup looks like:
I think it’s the first time in a long time when I don’t have too many CSS lines to show you. This time, less is more :)
The interesting part is related to the
.gallery:hover li:not(:hover) selector. When you hover over the list, we’ll assume you’ll hover also over a list element and we’ll apply some filters to the non hovered list elements.
This is how the other images looks like when the tulip image is hovered.
For this example I chose to use
font-size: 0 is my “kung-fu” move to fight the space between inline-block elements.
Regarding degradation, here’s my method:
If the browser support CSS filters and
:not, then apply filters and also decrease opacity.
If the browser does not support CSS filters (currently all except Canary) but it does support the
:not, then just decrease opacity.
If the browser is too old and does not support neither opacity nor
:notselector, then do nothing.
Here’s the current support for the CSS filter effects: Chrome 20.0.1123.0 (currently Canary) and Webkit nightly.
The future sounds good. We already have a Flexbox Module and CSS Filters, I like to think that in the near future we’ll also have variables and the CSS parent selector ready to use. Exciting times for web developers, don’t you think so?