summaryrefslogtreecommitdiffstats
path: root/chrome/browser/views
diff options
context:
space:
mode:
authorananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-04-16 01:26:08 +0000
committerananta@chromium.org <ananta@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2009-04-16 01:26:08 +0000
commit6b2ebf86a61169856aa3e650c294fd3511da5ee3 (patch)
tree738917bf517c07bfaf9fc4806dbd91f53df0c1fe /chrome/browser/views
parent0af12ab12a6888c29b631f58af5f9c28e99657b1 (diff)
downloadchromium_src-6b2ebf86a61169856aa3e650c294fd3511da5ee3.zip
chromium_src-6b2ebf86a61169856aa3e650c294fd3511da5ee3.tar.gz
chromium_src-6b2ebf86a61169856aa3e650c294fd3511da5ee3.tar.bz2
Fix a painting problem observed with windowless flash plugins, when they are initially created with a zero clip
rect, which eventually changes to a non zero clip rect. We don't send over geometry updates to the plugin if the window dimensions don't change, which is true in this case. This causes the plugin process to not send over paints to the renderer process as the plugin clip rect remains zero. The fix based on a discussion with John is to remove the check for whether the plugin dimensions changed and always send over the update geometry IPC to the plugin, where we do check whether these rects changed before calling the underlying plugin. This fixes bug http://code.google.com/p/chromium/issues/detail?id=10536 I am trying to come up with a unit test for this case. Will add it to this CB or submit those as a separate CB. Bug=10536 Review URL: http://codereview.chromium.org/73071 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@13822 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/views')
0 files changed, 0 insertions, 0 deletions