diff options
| author | pkasting@chromium.org <pkasting@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-01-13 00:55:40 +0000 |
|---|---|---|
| committer | pkasting@chromium.org <pkasting@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2009-01-13 00:55:40 +0000 |
| commit | 65a9344bc376424b38bb379e4f3feea5201423d2 (patch) | |
| tree | 9d5d3ee48495509e7b8f2bbd7971577d75300434 /webkit/glue/feed_preview.cc | |
| parent | 046344c69b0e16f8fa2fdcaf7a8e486d26301486 (diff) | |
| download | chromium_src-65a9344bc376424b38bb379e4f3feea5201423d2.zip chromium_src-65a9344bc376424b38bb379e4f3feea5201423d2.tar.gz chromium_src-65a9344bc376424b38bb379e4f3feea5201423d2.tar.bz2 | |
Pixel perfection on OTR icon. The tabstrip is still positioned/sized wrong relative to the OTR icon, sadly.
Much of the issue here is because the OTR image was a child view in the old code and isn't in the new. As a result, we have to:
* Change the drawing order to draw the OTR image after the tabstrip (like a child view would normally have been drawn), so the tabstrip's semi-transparent pixels don't overlay it
* Change the bounds calculation and drawing code to clip the image properly in maximized mode (where a child view would have been clipped naturally)
Since I changed the calling order of the OTR functions, I also changed their declaration/definition order to follow suit.
This also tries to rename a few constants to be more consistent. I can't figure out how to make any of these read nicely :(
BUG=5054
Review URL: http://codereview.chromium.org/17362
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@7908 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'webkit/glue/feed_preview.cc')
0 files changed, 0 insertions, 0 deletions