diff options
author | brettw@chromium.org <brettw@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-07-11 19:23:05 +0000 |
---|---|---|
committer | brettw@chromium.org <brettw@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-07-11 19:23:05 +0000 |
commit | e14774c883a1bda8609bc1ea21e85c1fbe44c5d6 (patch) | |
tree | 0d9efaef946244a7b9e7e0ee6881dc5005381eda /build/README.chromium | |
parent | 8445ced57bf8ec7de24558aa077d9c7f54a51f92 (diff) | |
download | chromium_src-e14774c883a1bda8609bc1ea21e85c1fbe44c5d6.zip chromium_src-e14774c883a1bda8609bc1ea21e85c1fbe44c5d6.tar.gz chromium_src-e14774c883a1bda8609bc1ea21e85c1fbe44c5d6.tar.bz2 |
Remove incorrect optimization for plugin binding. This would cause incorrect
invalidations when changing the bound graphics 2d of an instance.
The optimization is also no longer important since the new paint manager
will do the opposite of what the comment for the optimization was saying. The
paint manager now has plugins paint into the offscreen bitmap and then flush
the completed new image data to the instance all at once.
The sequence of operations that causes the problem is to bind a device and
paint it (order unimportant). Then bind a new fresh one at a smaller size,
and then paint it. Because of this optimization, the second bind wouldn't
invalidate, and then the subsequent paints to it would not invalidate outside
of the bounds of the new Graphics2D.
BUG=81475
Review URL: http://codereview.chromium.org/7326022
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@92036 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'build/README.chromium')
0 files changed, 0 insertions, 0 deletions