summaryrefslogtreecommitdiffstats
path: root/DEPS
diff options
context:
space:
mode:
authornduca@google.com <nduca@google.com@0039d316-1c4b-4281-b951-d872f2087c98>2012-03-24 09:27:28 +0000
committernduca@google.com <nduca@google.com@0039d316-1c4b-4281-b951-d872f2087c98>2012-03-24 09:27:28 +0000
commit5bb15df2e87609f8f19e75524af32afbd4f7ff13 (patch)
tree1035e57ee3d5f66544c3b0062ba094e91e2735f9 /DEPS
parent4f720bf83554462b711a4afd24cc632ce248510e (diff)
downloadchromium_src-5bb15df2e87609f8f19e75524af32afbd4f7ff13.zip
chromium_src-5bb15df2e87609f8f19e75524af32afbd4f7ff13.tar.gz
chromium_src-5bb15df2e87609f8f19e75524af32afbd4f7ff13.tar.bz2
Speculative Revert 128677 - Fix install-from-dmg.
When installing from a disk image, the browser relaunched from the newly-installed location should follow the proper first-run experience if appropriate. When installing from a disk image, existing dock tiles should be reused, and dock tiles pointing at the application on the disk image should be replaced with ones pointing at the newly-installed location. When installing from a disk image and requesting administrator access (because the user does not have permission to install to /Applications), Keystone should be promoted to a system-level install, and Chrome's Keystone ticket should be promoted to a system Keystone ticket. The custom panel key window tracking stuff doesn't need to maintain strong references to key windows, but does need to be beefed up for thread safety. Chrome doesn't need to wait until it's mostly started up to run the install-from-dmg flow. It should do it early, avoiding delays and reducing the possibility that harmful services will start running. BUG=119325 TEST=obvious from the above and the bug Review URL: http://codereview.chromium.org/9814029 TBR=mark@chromium.org Review URL: https://chromiumcodereview.appspot.com/9836082 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@128724 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'DEPS')
0 files changed, 0 insertions, 0 deletions