diff options
| author | qufighter@gmail.com <qufighter@gmail.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-03-06 19:06:57 +0000 |
|---|---|---|
| committer | qufighter@gmail.com <qufighter@gmail.com@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-03-06 19:06:57 +0000 |
| commit | 672485ba00d44d7c572ed101113f7c734c5f710d (patch) | |
| tree | ac02cf7c172b3ccd3bedbd336c20c22ba4458440 /chrome/browser/autofill/OWNERS | |
| parent | 0fe3643425848772210775ccd3bd37598372f90b (diff) | |
| download | chromium_src-672485ba00d44d7c572ed101113f7c734c5f710d.zip chromium_src-672485ba00d44d7c572ed101113f7c734c5f710d.tar.gz chromium_src-672485ba00d44d7c572ed101113f7c734c5f710d.tar.bz2 | |
captureVisibleTab Extension API producing garbled PNG results
Patch from Sam Larison <qufighter@gmail.com>
new DCHECK will fail if rowBytes() on SkBitmap is too low
"Windows drivers sometimes require that scanlines (rows in the image) be memory aligned. That is why they are sometimes larger than they would strictly need to be."
Instead of attempting to compute row bytes, we should be using the rowBytes() provided by SkBitmap
BUG=176062
TEST=The test case involves using the "Capture Visible Content" feature of the Google Screen Capture extension on a newly loaded http:// page after installation of the extension. The bug produces itself if after I size the window my window.innerWidth is 1000 or any other non-multiple of 16 (window.innerWidth % 16 != 0)
Review URL: https://chromiumcodereview.appspot.com/12313139
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@186472 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/autofill/OWNERS')
0 files changed, 0 insertions, 0 deletions