summaryrefslogtreecommitdiffstats
path: root/WebCore/css/themeChromiumLinux.css
diff options
context:
space:
mode:
authorMike Reed <reed@google.com>2009-09-25 14:45:42 -0400
committerMike Reed <reed@google.com>2009-09-25 15:47:14 -0400
commit01eae5621621a976f228f5f41c49967a356209cd (patch)
tree38fa6a2e6c7674d9873e36fb75eeb39e66d2d644 /WebCore/css/themeChromiumLinux.css
parent6f855d88ef8d1b401944d290772a26222b61a505 (diff)
downloadexternal_webkit-01eae5621621a976f228f5f41c49967a356209cd.zip
external_webkit-01eae5621621a976f228f5f41c49967a356209cd.tar.gz
external_webkit-01eae5621621a976f228f5f41c49967a356209cd.tar.bz2
fix cracks when we draw the page in portions (i.e. a picture set)
When we record/draw the DOM N times (for speed), webkit sees what we're doing in certain places, and sends us different rectangle coordinates. These were all being antialiased (by default). However, when we are also zoomed, the rects now fall on fractional coordinates, and with aa, we will double-draw the edges where those rects should have seamed. The fix is to disable antialiasing for a class of rects that we record from webkit. We are probably disabling for more cases than is necessary for the current bug, but knowing which ones are "required" is tricky, and there (as yet) seems to be no down-side, since we never draw the page rotated at a funny angle (where the rect edge would look jaggie). http://b/issue?id=2132971&cookieId=2009268114917835 http://b/issue?id=2127763&cookieId=2009268114931860
Diffstat (limited to 'WebCore/css/themeChromiumLinux.css')
0 files changed, 0 insertions, 0 deletions