New CSS filters are being developed and tested by Adobe in hopes of releasing them next year.
Play around with them here:
http://html.adobe.co...s/cssfilterlab/
IE Filters seem to be making a comeback in CSS3.
Started by flcl_grim, Nov 29 2012 12:21 AM
6 replies to this topic
#1
Posted 29 November 2012 - 12:21 AM
#2
Posted 29 November 2012 - 02:07 AM
People stopped using filters?
Every uncreative forum sig begs to differ.
But still, that's a neat find. I wonder what they will bring to the filter table.
Every uncreative forum sig begs to differ.
But still, that's a neat find. I wonder what they will bring to the filter table.
#3 Guest_ElatedOwl_*
Posted 29 November 2012 - 08:27 AM
The filter prop itself is fairly new - but text-stroke (aka drop shadow) and box-shadow (aka glow) have been out for a while.
I'm not entirely sure how I feel about it, some of the filters are really resource hungry.
(also, adobe isn't developing them. >.> there's a guy from adobe on the w3 board I believe, but the browser vendors are the ones who actually have to develop it)
I'm not entirely sure how I feel about it, some of the filters are really resource hungry.
(also, adobe isn't developing them. >.> there's a guy from adobe on the w3 board I believe, but the browser vendors are the ones who actually have to develop it)
#4
Posted 29 November 2012 - 02:05 PM
That is what bothers me. w3 was created as a method of standardizing the web.
Yet webkit, gecko, and other engines are trying to ruin that by introducing their own implementations of the same ideas.
I, personally, blame <blink> for starting it all.
Yet webkit, gecko, and other engines are trying to ruin that by introducing their own implementations of the same ideas.
I, personally, blame <blink> for starting it all.
#5 Guest_ElatedOwl_*
Posted 29 November 2012 - 03:13 PM
Actually, the w3 board is comprised of people from all of the major vendors. I *think* adobe has a spot, I know MS/google and moz have a spot.
When they do stuff with vendor specific prefixes (ie -webkit-transition) it's simply because its not ready to be released yet, but the stuff is in the draft.
When they do stuff with vendor specific prefixes (ie -webkit-transition) it's simply because its not ready to be released yet, but the stuff is in the draft.
#6
Posted 29 November 2012 - 11:21 PM
Oh, okay. That makes a bit more sense.
So is HTML5 not actually web standard yet, or are the exclusive tags just further implementations that have not been absorbed by the standard?
So is HTML5 not actually web standard yet, or are the exclusive tags just further implementations that have not been absorbed by the standard?