W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > March 2010

[Bug 9329] New: drawImage filtering when dx and dy aren't integers needs defined

From: <bugzilla@wiggum.w3.org>
Date: Fri, 26 Mar 2010 04:34:14 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-9329-2486@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=9329

           Summary: drawImage filtering when dx and dy aren't integers needs
                    defined
           Product: HTML WG
           Version: unspecified
          Platform: PC
        OS/Version: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: HTML5 spec bugs
        AssignedTo: dave.null@w3.org
        ReportedBy: warcraftthreeft@sbcglobal.net
         QAContact: public-html-bugzilla@w3.org
                CC: ian@hixie.ch, mike@w3.org, public-html@w3.org


I noticed that currently Firefox and Chrome draw things differently when given
a dx and dy that are not integers. Firefox uses bilinear filtering and chrome
uses nearest neighbor rounding the dx and dy values. This can be tested by
rendering an image at 0.0, 0.1, etc to 1.0. There should probably be a defined
operation that should occur or there should be a way to define which one the
user wants. I prefer nearest neighbor, but I know not everyone likes pixel
snapping.

Currently the only way to get similar behavior in both browsers is to wrap dx
and dy in Math.round before passing them to drawImage, but that gets rid of the
bilinear filtering that users might want.


-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 26 March 2010 04:34:17 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 26 March 2010 04:34:26 GMT