diff options
| author | wez@chromium.org <wez@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-01-02 18:02:27 +0000 |
|---|---|---|
| committer | wez@chromium.org <wez@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2013-01-02 18:02:27 +0000 |
| commit | f1a553602b8ae993ae4c19b7abceebeb923b44b6 (patch) | |
| tree | a0353afaff94fa5fa13d5346ff2407cdce30da3d /content/shell/mac | |
| parent | 4ef04de1eb73971729867045567a5d2437dfd933 (diff) | |
| download | chromium_src-f1a553602b8ae993ae4c19b7abceebeb923b44b6.zip chromium_src-f1a553602b8ae993ae4c19b7abceebeb923b44b6.tar.gz chromium_src-f1a553602b8ae993ae4c19b7abceebeb923b44b6.tar.bz2 | |
Allow NPAPI & Trusted Broker plugins access to OS-level HighDPI APIs.
As per crrev.com/10069029, OS 10.7.3 and above report low-DPI to
processes that lack an NSPrincipalClass key in their manifest. Because
Chromium Helper processes lacked this key, NPAPI or Trusted Broker
plugins they hosted could not use the OS HighDPI APIs.
This CL adds the key to Chromium's Helper process plist, so that APIs
such as -[NSScreen backingScaleFactor] will now return 2 under HighDPI.
Note that NPAPI plugins still can't paint HighDPI surfaces yet because
chrome doesn't implement the NPAPI ContentsScaleFactor specification
(see crbug.com/31960).
BUG=167209
Review URL: https://chromiumcodereview.appspot.com/11642052
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@174811 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'content/shell/mac')
| -rw-r--r-- | content/shell/mac/helper-Info.plist | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/content/shell/mac/helper-Info.plist b/content/shell/mac/helper-Info.plist index 646d48f..d3ab6e3 100644 --- a/content/shell/mac/helper-Info.plist +++ b/content/shell/mac/helper-Info.plist @@ -24,6 +24,8 @@ <string>${MACOSX_DEPLOYMENT_TARGET}.0</string> <key>LSUIElement</key> <string>1</string> + <key>NSPrincipalClass</key> + <string>CrApplication</string> <key>NSSupportsAutomaticGraphicsSwitching</key> <true/> </dict> |