This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: https://html.spec.whatwg.org/multipage/scripting.html Multipage: https://html.spec.whatwg.org/multipage/#pixel-manipulation Complete: https://html.spec.whatwg.org/#pixel-manipulation Referrer: https://html.spec.whatwg.org/multipage/ Comment: Comment about canvas high-res outdated? // notice that we are using input.width and input.height here // as they might not be the same as canvas.width and canvas.height // (in particular, they might be different on high-res displays) Is this correct given https://html5.org/r/8397 ? Posted from: 90.230.218.37 by simonp@opera.com User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/41.0.2272.35 Safari/537.36 OPR/28.0.1750.15 (Edition beta)
hello, could you give some more details for the issue, thanks!
I guess the comment could be updated to say something like "In this case, input.width and input.height match canvas.width and canvas.height, but we'll use the former to make the code more generic."
"In this case we are using, input.width and input.height which match canvas.width and canvas.height, but we'll use the former to make the code more generic." Is this good?(just gave a try)
Maybe it's better to keep it simpler: "input.width and input.height happen to match canvas.width and canvas.width, but we'll use the former to keep the code generic."
okay right, cool.
https://github.com/whatwg/html/pull/669