Issue 62100: Avoid Google Chrome/Chromium default browser conflict by renaming Capabilities key.

Keyboard Shortcuts

	File
u :	up to issue
j / k :	jump to file after / before current file
J / K :	jump to next file with a comment after / before current file
	Side-by-side diff
i :	toggle intra-line diffs
e :	expand all comments
c :	collapse all comments
s :	toggle showing all comments
n / p :	next / previous diff chunk or comment
N / P :	next / previous comment
<Up> / <Down> :	next / previous line

	Issue
u :	up to list of issues
j / k :	jump to patch after / before current patch
o / <Enter> :	open current patch in side-by-side view
i :	open current patch in unified diff view

	Issue List
j / k :	jump to issue after / before current issue
o / <Enter> :	open current issue

Issue 62100: Avoid Google Chrome/Chromium default browser conflict by renaming Capabilities key. (Closed)

Created:
11 years, 8 months ago by kuchhal

Modified:
9 years, 7 months ago

Reviewers:
huanr

CC:
chromium-reviews_googlegroups.com

Visibility:
Public.

Avoid Google Chrome/Chromium default browser conflict by renaming Capabilities key. BUG=9697

Created: 11 years, 8 months ago

Download [raw] [tar.bz2]

		Unified diffs	Side-by-side diffs	Delta from patch set	Stats (+32 lines, -41 lines)			Patch
	M	chrome/installer/setup/uninstall.cc	View	1	1 chunk	+7 lines, -1 line	0 comments	Download
	M	chrome/installer/util/shell_util.cc	View	1	2 chunks	+25 lines, -40 lines	0 comments	Download

Total messages: 2 (0 generated)

kuchhal

We call Vista API to verify default browser which checks under RegisteredApplication registry key based ...

11 years, 8 months ago (2009-04-07 11:35:16 UTC) #1

LGTM