RESOLVED FIXED89618
Unskip fast/hidpi/device-scale-factor-paint.html 
https://bugs.webkit.org/show_bug.cgi?id=89618
Summary Unskip fast/hidpi/device-scale-factor-paint.html
Adam Barth
Reported 2012-06-20 17:09:49 PDT
Unskip fast/hidpi/device-scale-factor-paint.html
Attachments
Patch (18.27 KB, patch)
2012-06-20 17:11 PDT, Adam Barth 		no flags
DetailsFormatted DiffDiff
Patch (18.36 KB, patch)
2012-06-20 17:12 PDT, Adam Barth 		no flags
DetailsFormatted DiffDiff
Show Obsolete (1) View All Add attachment proposed patch, testcase, etc.
Adam Barth
Comment 1 2012-06-20 17:11:48 PDT
Created attachment 148684 [details] Patch
Adam Barth
Comment 2 2012-06-20 17:12:55 PDT
Created attachment 148685 [details] Patch
Adam Barth
Comment 3 2012-06-20 17:35:09 PDT
tdanserson: Notice that apple-mac seems to produce large PNGs for these hidpi test results. I'm not sure what all is involved in teaching Chromium's DRT to produce big PNGs.
WebKit Review Bot
Comment 4 2012-06-20 18:29:53 PDT
Comment on attachment 148685 [details] Patch Clearing flags on attachment: 148685 Committed r120894: <http://trac.webkit.org/changeset/120894>
WebKit Review Bot
Comment 5 2012-06-20 18:29:58 PDT
All reviewed patches have been landed. Closing bug.
Terry Anderson
Comment 6 2012-06-21 11:35:48 PDT
(In reply to comment #3) > tdanserson: Notice that apple-mac seems to produce large PNGs for these hidpi test results. I'm not sure what all is involved in teaching Chromium's DRT to produce big PNGs. I thought we had agreed that we would be keeping the PNGs at the normal 800x600 size, which would show just the top left quadrant of the image.
Adam Barth
Comment 7 2012-06-21 12:06:17 PDT
> I thought we had agreed that we would be keeping the PNGs at the normal 800x600 size, which would show just the top left quadrant of the image. If we go that route, we should convert these tests to that format as well. On the other hand, it might be easier to build on what we have already. In any case, we should end up with this working the same way for every port.
Note You need to log in before you can comment on or make changes to this bug.