summaryrefslogtreecommitdiffstats
path: root/chrome/common/font_loader_mac.mm
diff options
context:
space:
mode:
authorasargent@chromium.org <asargent@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-09-23 20:19:56 +0000
committerasargent@chromium.org <asargent@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98>2010-09-23 20:19:56 +0000
commite558ff82d3f37169fad4abd52200dc75651a3ab5 (patch)
tree5eeea1786cec4171e7fe4179413865dea9a4b426 /chrome/common/font_loader_mac.mm
parent24dc637a97bb646e5d41129f2daa0949edade2bf (diff)
downloadchromium_src-e558ff82d3f37169fad4abd52200dc75651a3ab5.zip
chromium_src-e558ff82d3f37169fad4abd52200dc75651a3ab5.tar.gz
chromium_src-e558ff82d3f37169fad4abd52200dc75651a3ab5.tar.bz2
Add a launchApp method to extension management API.
This makes it possible for new tab replacement extensions to recreate the same app launch experience as the built-in NTP (pinned tabs, launch containers, etc.) Also add the extension version to data we report about extensions via the management API. BUG=56325,55474 TEST=An extension using chrome.experimental.management.launchApp(<id>) should work to launch an app the same way that app gets launched from the built-in new tab page. Review URL: http://codereview.chromium.org/3381019 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@60334 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/common/font_loader_mac.mm')
0 files changed, 0 insertions, 0 deletions