diff options
author | petewil@chromium.org <petewil@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-06-01 04:21:36 +0000 |
---|---|---|
committer | petewil@chromium.org <petewil@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-06-01 04:21:36 +0000 |
commit | ffa4a92905391a8a42a9c8e24be8908833dee56f (patch) | |
tree | 64c6093e3aa2ae766a2e5b326b2455ca67a850c4 /tools/gdb/gdb_chrome.py | |
parent | dbd6fe46d8f500df55d6959a6f0850fbc81c6de0 (diff) | |
download | chromium_src-ffa4a92905391a8a42a9c8e24be8908833dee56f.zip chromium_src-ffa4a92905391a8a42a9c8e24be8908833dee56f.tar.gz chromium_src-ffa4a92905391a8a42a9c8e24be8908833dee56f.tar.bz2 |
Continue bitmap fetching for notifications.
This continues the bitmap fetching for notifications feature by adding the actual bitmap URL fetching and decoding.
This checkin adds a new class, NotificationBitmapFetcher,
which is responsible for fetching the URL of the bitmap to
get the bitmap bits, and decoding them into an SkBitmap for
eventual passing to the Rich Notifications system.
Along with the class I add unit tests (for testing the synchronous parts) and browser tests (for testing the async parts) of the checkin.
The current approach uses URLFetcher and ImageDecoder (on a different thread). The call flow is first to call the URLFetcher, and when it returns async, to call the ImageDecoder in a different process so that any bitmap decoding errors do not result in a security hole.
BUG=241829
Review URL: https://chromiumcodereview.appspot.com/15295018
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@203566 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'tools/gdb/gdb_chrome.py')
0 files changed, 0 insertions, 0 deletions