- From: SVG Working Group Issue Tracker <sysbot+tracker@w3.org>
- Date: Tue, 29 Jun 2010 19:58:36 +0000
- To: public-svg-wg@w3.org
ISSUE-2346: previous discussion about filterRes [SVG 1.1 F2 Last Call] http://www.w3.org/Graphics/SVG/WG/track/issues/2346 Raised by: Erik Dahlström On product: SVG 1.1 F2 Last Call I think, the previous discussion about filterRes could be reflected within the related section, for example as an informative addition. Previous discussion: http://lists.w3.org/Archives/Public/www-svg/2009Jul/0014.html http://lists.w3.org/Archives/Public/www-svg/2009Jul/0017.html http://lists.w3.org/Archives/Public/www-svg/2009Jul/0020.html http://lists.w3.org/Archives/Public/www-svg/2009Jul/0029.html Summary: a) Problem with float numbers and rounding in implementations Suggestion: Note, that behaviour for float numbers is undefined, therefore authors should use only integers. Note furthermore, that this might cause implementation dependent behaviour for continuous animation, in doubt authors have to use discrete animation providing all intended values manually. Alternatively define the behaviour for float numbers. b) To which value in pixels results the mentioned 'default' of 400dpi? What does 'current display's pixel resolution' mean? For example, if the filter region is related to an area of 1000px x 600px device pixels, is the related value '1000 600'? Or does it mean for the same device with a display of 1600px x 1200px a value of '1600 1200'? Suggestion: Explain how to derive the required number value for filterRes from the mentioned '400dpi default'. Alternatively avoid to mention units for an attribute value, that can only contain numbers. Provide an example for a device display and a filter region as mentioned. Original mail: http://lists.w3.org/Archives/Public/www-svg/2010Jun/0202.html
Received on Tuesday, 29 June 2010 19:58:39 UTC