| commit | 3d77b5b0d0d394ab34712a7bfd4ec76cbde2d77f | |
| author | yzshen@chromium.org <yzshen@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Sun, 3 Feb 2013 04:59:50 +0000 (3 04:59 +0000) | ||
| committer | yzshen@chromium.org <yzshen@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | |
| Sun, 3 Feb 2013 04:59:50 +0000 (3 04:59 +0000) | ||
| tree | cfd7c1b90ac00439cd695c54d75da19beffb56b7 | treesnapshot (tar.gz zip) |
| parent | bcb6ee23dd5d6fe711f702a3d04e8412dbf60804 | commitdiff |
Fix enable state of Pepper Flash.
Component-updated and bundled Pepper Flash share the same enable state. When
reading from the Preferences file, the previous code ignored the enable state
if it was associated with the component-updated path. That was wrong because if
the component-updated Flash was newer, the enable state would be recorded with
that path. The outcome was that everytime users restarted the browser, Pepper
Flash was enabled, even if they disabled it before.
TBR=bauerb@chromium.org
BUG=150596
TEST=None
Review URL: https://codereview.chromium.org/12079044
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@180288 0039d316-1c4b-4281-b951-d872f2087c98
Component-updated and bundled Pepper Flash share the same enable state. When
reading from the Preferences file, the previous code ignored the enable state
if it was associated with the component-updated path. That was wrong because if
the component-updated Flash was newer, the enable state would be recorded with
that path. The outcome was that everytime users restarted the browser, Pepper
Flash was enabled, even if they disabled it before.
TBR=bauerb@chromium.org
BUG=150596
TEST=None
Review URL: https://codereview.chromium.org/12079044
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@180288 0039d316-1c4b-4281-b951-d872f2087c98
| chrome/browser/plugins/plugin_prefs.cc | diffblobblamehistory | |
| chrome/browser/plugins/plugin_prefs.h | diffblobblamehistory |