Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

    CSS filters are already in Chrome and Safari, and allow advanced styling as as blurring, warping and modifying the color intensities of elements. 
Isn't it funny that the first browser to implement these "filters" was IE 4.0 [1]. And at that time using any of these filters was a bit frowned upon and amateurish. Now suddenly everyone is gung-ho about it and calling it the API that will transform the web in 2013.

[1] http://msdn.microsoft.com/en-us/library/ms532849(v=vs.85).as...



Except IE's filters were an unrelated proprietary technology with an ugly syntax:

  filter: progid:DXImageTransform.Microsoft.Blur(pixelradius=2);
compared to

  filter: blur(2px);


Actually the first syntax was introduced in IE 5.5. The second is very similar to the IE4 syntax, so why not make it compatible?


GLSL isn't exactly beautiful all the time...


You can always write this in IE.

    filter: Blur(pixelradius=2);


Similar to how IE's box model was deemed incorrect until fast-forward today and people realized that their box model was simpler and easier to use compared to the standard. See: http://paulirish.com/2012/box-sizing-border-box-ftw/


Sure, but IE screwed up more things than it got right. Way more.


http://hsivonen.iki.fi/almost-precedent/

There is a reason why WHATWG considers HTML a living standard.



IE7 got rid of DirectAnimation, which is basically DirectX in IE, since IE4.

And now there's WebGL.

And other features like

- DirectMusic (MIDI support)

- VRML (which is basically SVG)

- dHTML+TIME (animiation support)

- page transition effects

- render doc/ppt/xls in html

- .htc as web components


VRML (which is basically SVG)

Not really; VRML was a 3D modeling language, while SVG is for 2D images/animations.





Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: