This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
filterRes has been removed from the Filter Effects spec: http://dev.w3.org/fxtf/filters/#element-attrdef-filterres
Does anyone implement <filterRes>?
(In reply to Ian 'Hixie' Hickson from comment #1) > Does anyone implement <filterRes>? It's an attribute on the <filter> element (e.g. <filter filterRes="5 5" .../>). Safari and Chrome implement it when the filter is applied on SVG content. It does not work on HTML content in either browser. Firefox implements it right now but is in the process of removing it. I'm not sure what IE does. Interestingly, the renderings for each browser vary vastly for the simplest test cases.
Created attachment 1445 [details] Simple SVG Content Test Case: filterRes of "5 5" on left box, no filterRes on right box
Created attachment 1446 [details] Simple HTML Content Test Case: filterRes of "5 5" on left box, no filterRes on right box
Well if some browsers support it, it seems better to leave it. Any idea why Gecko is removing it? Will other browsers follow suit?
To be clear, Max is removing it from Gecko (with my approval). AFAIK filterRes is very little used. It's not very well designed. I think removing it is safe because we'll fall back to picking the resolution ourselves instead, which is generally the best thing to do anyway. It adds significant code complexity.
Chrome guys are looking into this too: https://code.google.com/p/chromium/issues/detail?id=353272
Ok, I've removed it.
Checked in as WHATWG revision r8554. Check-in comment: Drop filterRes SVG attribute from the HTML parser, since it has fallen into disrepute. http://html5.org/tools/web-apps-tracker?from=8553&to=8554