diff options
| author | garykac@chromium.org <garykac@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-11-16 01:09:31 +0000 |
|---|---|---|
| committer | garykac@chromium.org <garykac@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2012-11-16 01:09:31 +0000 |
| commit | 016b57f941ec02b4342bb2fefb4bae5f83d10a9f (patch) | |
| tree | 83a9519106c53e79ec02059c19daf1f161b08078 /chrome/browser/first_run | |
| parent | 8ed949ae618f8683e7e2b377103dc39bdac7d162 (diff) | |
| download | chromium_src-016b57f941ec02b4342bb2fefb4bae5f83d10a9f.zip chromium_src-016b57f941ec02b4342bb2fefb4bae5f83d10a9f.tar.gz chromium_src-016b57f941ec02b4342bb2fefb4bae5f83d10a9f.tar.bz2 | |
Revert 168080 - Configure system-level Chrome settings (i.e. install its shortcuts) immediately following self-destruction of a user-level Chrome.
Also refactor RemoveShortcut() to use base::win::ResolveShortcut() instead of coming up with its own method (which I'm scared could still hold handles to the shortcut when trying to delete it; doesn't seem to have been a problem, but I'd rather be safe).
BUG=158524
TEST=Install user-level Chrome on user A, install system-level Chrome on user B (while A is still logged in), go back to user A and run Chrome, user-level Chrome self-destructs and new shortcuts are installed pointing to system-level Chrome.
Review URL: https://chromiumcodereview.appspot.com/11359219
TBR=gab@chromium.org
Review URL: https://codereview.chromium.org/11299024
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@168099 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/first_run')
0 files changed, 0 insertions, 0 deletions