| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Chrome App Host is a simple exe that delegates to a Chrome Binaries installation at user or system level. If no installation is available, it will trigger an installation.
The Chrome App Host prevents the Chrome Binaries from being uninstalled, except in the case of an upgrade to system-level.
The Chrome App Host is implemented in this uncommitted CL: http://codereview.chromium.org/10559090/ .
BUG=None
TEST=None
Review URL: https://chromiumcodereview.appspot.com/10665002
TBR=erikwright@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10797047
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@147668 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This commit also adds --configure-user-settings flag to setup.exe which Active Setup will invoke at user login on system-level installs. For now this flag doesn't do anything (it will be implemented in a follow up CL).
Active Setup design doc: https://docs.google.com/a/chromium.org/document/d/1yQdG1wMDKi_lf0i8bk6P2_BWqudRb-ap6Y2C5f1RO2w/edit
This CL also introduces ScopedTokenPrivilege, a class meant to give the current process's token privileges for a short period of time while some critical operations (loading other users' registry hives) are happening.
BUG=132825
TEST=From an admin prompt: setup_unittests.exe --gtest_filter=SetupUtilTest.ScopedTokenPrivilege*
Windows only calls Active Setup's StubPath (i.e. setup.exe --configure-user-settings) if:
1) It never called it before (i.e. the HKCU equivalence of the Chrome Active Setup doesn't exist for this user).
or
2) The version in HKLM is greater than the version in HKCU (i.e. Chrome has been updated since the last user login).
Uninstalling Chrome deletes the HKCU entries for all users (logged in or not).
Later reinstalling an older version of Chrome (just reinstall and manually hack the HKLM Active Setup version) has every user go through Active Setup again (if we didn't delete the values ourselves it wouldn't... which is why I had to introduce 75% of this CL simply to delete the HKCU Active Setup entries created by Windows for every user...)
Review URL: https://chromiumcodereview.appspot.com/10810021
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@147667 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As of http://lists.cs.uiuc.edu/pipermail/cfe-commits/Week-of-Mon-20120716/061102.html
the warning finds more bugs. Fix them.
BUG=none
TEST=none
TBR=owners
Review URL: https://chromiumcodereview.appspot.com/10800052
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@147666 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Chrome App Host is a simple exe that delegates to a Chrome Binaries installation at user or system level. If no installation is available, it will trigger an installation.
The Chrome App Host prevents the Chrome Binaries from being uninstalled, except in the case of an upgrade to system-level.
The Chrome App Host is implemented in this uncommitted CL: http://codereview.chromium.org/10559090/ .
BUG=None
TEST=None
Review URL: https://chromiumcodereview.appspot.com/10665002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@147650 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
commands via Google Update.
In http://codereview.chromium.org/10665002/ :
setup.exe is used by the 'quick-enable-application-host' app command.
app_host.exe is used by the 'install-application' app command.
Pending Omaha changes will require executables referenced by app commands to include a resource marker. This CL adds that marker to the appropriate exes.
BUG=None
TEST=None
Review URL: https://chromiumcodereview.appspot.com/10795026
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@147552 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
The logo is added in another patch to metro_driver.dll.
BUG=129598
TEST=Test pages can be pinned in metrod chrome.
Review URL: https://chromiumcodereview.appspot.com/10689187
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@147345 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
(otherwise only half (the common half...:( ) of the sid string would get encoded...)
this change is super trivial and only fixes the resulting suffix
R=grt@chromium.org
BUG=133810
TEST=Make sure Chrome gets the proper suffix
Review URL: https://chromiumcodereview.appspot.com/10703147
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@146217 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
For context see this thread:
https://groups.google.com/a/chromium.org/forum/?fromgroups#!topic/chromium-dev/RMcVNGjB4II
TBR=thakis,pkasting,jam
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@146163 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=none
TEST=none
TBR=sky@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10683005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@146157 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
R=grt@chromium.org
BUG=108171
Review URL: https://chromiumcodereview.appspot.com/10694109
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@145716 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is necessary as the follow-up patches will need a clean way to call CreateOrUpdateChromeShortcuts() while knowing the outcome which was kind of vague before (and would have required passing in a fake InstallStatus to simulate the desired behaviour...).
BUG=132825, 127544, 131415
TEST=Install Chrome at user and system-level with and without create_all_shortcuts and verify that shortcut creation is as expected.
Over-install this custom installer over chrome-dev after having deleted its shortcuts and verify they are not recreated.
Review URL: https://chromiumcodereview.appspot.com/10692034
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@145609 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the MSDN rules (2nd try).
The suffix will now be the base32 encoding of the md5 hash of the user's username. This is always unique and can be determined many times deterministically without I/O access (as opposed to other methods we considered).
It respects all MSDN constraints for properties onto which it is appended.
This replaces the prior-style username suffixes for new installs.
Old-style suffixes (i.e. unsuffixed and username suffixed) will however be kept as is through future updates.
Design doc: https://docs.google.com/a/chromium.org/document/d/1qmcV3uYBh3JwvXhYkI7asg0nN7KfVMWVOzND4p0jQ3E/edit
Note: This is the continuation of http://codereview.chromium.org/10617002/ which was reverted in https://chromiumcodereview.appspot.com/10667006/
BUG=133810, 133173
TEST= http://goo.gl/ZZ7gE
installer_util_unittests.exe --gtest_filter=ShellUtilTest.*
Review URL: https://chromiumcodereview.appspot.com/10662052
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@145596 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
-- it's a user visible string
BUG=None
TEST=No suffix is displayed when selecting defaults on Windows for user-level installs.
Review URL: https://chromiumcodereview.appspot.com/10697075
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@145460 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
DelegateExecute handler under the Metro Chrome HKCR\<Chrome>/Chromium
key. This is needed for the opennewwindow operation on the chrome metro tile to work correctly.
This fix only ensures that metro chrome launches when we select the open new window operation on the metro tile. Other fixes are needed
to ensure that subsequent open new window operations cause new tabs to get created.
BUG=135122
R=gab
Review URL: https://chromiumcodereview.appspot.com/10698086
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@145383 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
signing.
The implied designated requirement produced when signing on Lion cannot be
satisfied on pre-Lion systems. This was already addressed by providing an
explicit designated requirement for the outer .app bundle. This change also
provides an explicit designated requirement for inner components.
The Parental Controls feature apparently requires an application to meet its
designated requirement. Since the requirement for inner components such as
the helper would never be met on 10.6 (or presumably 10.5), it was impossible
to launch such inner components. This prevented any renderer processes from
ever starting up. The user would only see sad tabs and endless OS prompts, and
the browser would effectively be useless.
BUG=131682, 134311
TEST=Turn on Parental Controls and set it to limit applications. Launch Chrome.
After a possible initial prompt asking whether Chrome should be permitted
(authenticate and say yes), Chrome should function normally. There should
be no prompts about Chrome Helper, Chrome Helper EH, or Chrome Helper NP.
Web pages should load normally. There should be no sad tabs. Note that
there may still be a prompt about ksadmin.
Review URL: https://chromiumcodereview.appspot.com/10696101
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@145370 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
install.cc
(also correct comments and do some string16 munging)
BUG=132825, 127544
TEST=None
Review URL: https://chromiumcodereview.appspot.com/10693032
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@145092 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=128663
R=brettw@chromium.org,willchan@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10669038
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@145073 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
As a precursor to extracting the install logic in subfunctions, might as well remove this flag which we decided was never used and is no longer needed (it was originally meant for Chrome Frame, but the installer path for CF now does this correctly without this flag).
BUG=132825,127544
TEST=Install CF with "setup.exe --chrome-frame --do-not-register-for-update-launch --do-not-launch-chrome" and ensure no shortcuts are created.
Review URL: https://chromiumcodereview.appspot.com/10700008
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@144580 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
running chrome.
BUG=NONE
TEST=NONE
Review URL: https://chromiumcodereview.appspot.com/10682006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@144466 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
NaCL doesn't build with ninja on account of http://crbug.com/127510. NaCL can be disabled via a GYP define, but the mini_installer hasn't been made aware of this until now.
BUG=none
TEST=none
Review URL: https://chromiumcodereview.appspot.com/10535050
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@144273 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
while respecting the MSDN rules. (Triggered assertion failures in browser_tests blocking WebKit rolls.)
The suffix will now be the base32 encoding of the md5 hash of the user's username. This is always unique and can be determined many times deterministically without I/O access (as opposed to other methods we considered).
It respects all MSDN constraint for properties onto which it is appended.
This replaces the prior-style username suffixes for new installs.
Old-style suffixes (i.e. unsuffixed and username suffixed) will however be kept as is through future updates.
Design doc: https://docs.google.com/a/chromium.org/document/d/1qmcV3uYBh3JwvXhYkI7asg0nN7KfVMWVOzND4p0jQ3E/edit
BUG=133810
TEST= http://goo.gl/ZZ7gE
installer_util_unittests.exe --gtest_filter=ShellUtilTest.*
Review URL: https://chromiumcodereview.appspot.com/10617002
TBR=gab@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10667006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@143833 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
the MSDN rules.
The suffix will now be the base32 encoding of the md5 hash of the user's username. This is always unique and can be determined many times deterministically without I/O access (as opposed to other methods we considered).
It respects all MSDN constraint for properties onto which it is appended.
This replaces the prior-style username suffixes for new installs.
Old-style suffixes (i.e. unsuffixed and username suffixed) will however be kept as is through future updates.
Design doc: https://docs.google.com/a/chromium.org/document/d/1qmcV3uYBh3JwvXhYkI7asg0nN7KfVMWVOzND4p0jQ3E/edit
BUG=133810
TEST= http://goo.gl/ZZ7gE
installer_util_unittests.exe --gtest_filter=ShellUtilTest.*
Review URL: https://chromiumcodereview.appspot.com/10617002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@143782 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=None
TEST=None
Review URL: https://chromiumcodereview.appspot.com/10663002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@143732 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The new UI supports both dialog and in-tab versions. Its purpose is to
set Chrome as default browser when running first time and to re-launch it
in Metro mode.
R=grt,gab,jhawkins,sky
BUG=131838
TEST=
Review URL: https://chromiumcodereview.appspot.com/10539169
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@143729 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Besides these two clients, will also be used by the Chrome Application Host stub.
R=robertshield,abodenha
CC=grt
BUG=None
TEST=None
Review URL: https://chromiumcodereview.appspot.com/10546149
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@143423 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
Adjust DCHECKs in base::win::SetAppIdForPropertyStore() to reflect the new appid standard which requires less than 64 characters, not 128 (as of Windows 8, see Metro guidelines for details).
BUG=133176
TEST=Chrome installs, launches, and multi-profile OS integration works for user-level installs (on a user with a space in username).
Review URL: https://chromiumcodereview.appspot.com/10559097
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@143290 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
Patch From Gabriel Charette <gab@chromium.org>
BUG=132991
TEST=Chrome Metro tile appears immediately after making Chrome default.
Review URL: https://chromiumcodereview.appspot.com/10576009
Patch from Gabriel Charette <gab@chromium.org>.
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@142911 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
ShellIntegration::GetAppId() --> ShellIntegration::GetProfileAppId() for clarity (i.e. having two functions called "GetAppId" is confusing imo).
Patch From Gabriel Charette <gab@chromium.org>
BUG=125362, 133173
TEST=Make sure 125362 doesn't repro.
http://goo.gl/ZZ7gE
ShellIntegrationTest.GetAppModelIdForProfileTest
ShellUtilTest.BuildAppModelId*
SessionRestoreTest.RestoreAfterClosingTabbedBrowserWithAppAndLaunching
AppModeTest.EnableAppModeTest
Review URL: https://chromiumcodereview.appspot.com/10542031
Patch from Gabriel Charette <gab@chromium.org>.
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@142909 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
This will pop the Greg dialog on Win8 when the installer is run as an interactive user with --make-chrome-default.
BUG=133119,113326
TEST=on win8: install chrome with --make-chrome-default 1) at user-level, 2) at system-level as a regular user, 3) at system-level as SYSTEM. 1 and 2 should show the default browser dialog, whereas 3 should just register it so that a user can make it the default without uac. on win7: everything should work as before.
Review URL: https://chromiumcodereview.appspot.com/10558015
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@142727 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=124013,125362, 133173
TEST=No UAC on first run for user-level installs on Win8.
http://goo.gl/ZZ7gE
Review URL: https://chromiumcodereview.appspot.com/10399054
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@142648 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=124013, 125362, 133173
TEST=http://goo.gl/ZZ7gE
Review URL: https://chromiumcodereview.appspot.com/10446111
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@142641 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This also adds the same suffixing to Chrome's appname for Default Programs registration (this suffix is not user-facing though as we don't suffix the actual string representing Chrome in the UI... obviously!)
Design doc: https://docs.google.com/a/chromium.org/document/d/1qmcV3uYBh3JwvXhYkI7asg0nN7KfVMWVOzND4p0jQ3E/edit
BUG=125362,124013,133173
TEST=http://goo.gl/ZZ7gE
Review URL: https://chromiumcodereview.appspot.com/10451074
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@142634 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
It will be needed in webkit/dom_storage/.
BUG=NONE
TEST=Existing tests.
Review URL: https://chromiumcodereview.appspot.com/10540003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@142142 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Some of our registry lookups were wrong based on how the "new" (Win7+) Windows operates.
BUG=None
TEST=None
Review URL: https://chromiumcodereview.appspot.com/10535057
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@141903 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=122756
TEST=None
Review URL: https://chromiumcodereview.appspot.com/10512026
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@141488 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=132037
TEST=installer_util_unittests.exe --gtest_filter=DeleteRegValueWorkItemTest.DeleteExistingValue
Review URL: https://chromiumcodereview.appspot.com/10535104
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@141412 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
This change disables SessionBackendTest.EmptyCommand and DeleteRegValueWorkItemTest.DeleteExistingValue on the debug bots of Windows because they cause assertion errors on VS2010.
TBR=marja,grt,robertshield,tommi
BUG=132037
TEST=make the "XP Tests (dbg)(1)" bot and the "Win7 Tests (dbg)(1)" bot green.
Review URL: https://chromiumcodereview.appspot.com/10537098
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@141386 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
|unique_suffix| in ShellUtil::RegisterChromeBrowser()
BUG=None
TEST=None
Review URL: https://chromiumcodereview.appspot.com/10535061
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@141230 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
latter whenever necessary.
R=grt@chromium.org, sky@chromium.org
BUG=113326, 129232
TEST=N/A
Review URL: https://chromiumcodereview.appspot.com/10453041
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@141172 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This removes the at-launch reauthorization step, but retains the at-update
reauthorization step for user Keystone tickets. The at-update helper stubs are
now prebuilt binaries signed with the old certificate, so the old target for
the stubs is removed and replaced with a straight file copy.
The new designated requirement only allows access to Keychain items for Chrome
official builds (canary and non-Canary) signed by the new Developer ID
certificate.
BUG=116210
TEST=none
Review URL: https://chromiumcodereview.appspot.com/10534027
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@140817 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
builds.
BUG=NONE
TEST=NONE
Review URL: https://chromiumcodereview.appspot.com/10546018
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@140796 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=none
TEST=none
Review URL: https://chromiumcodereview.appspot.com/10465003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@140136 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
...and switch to oh so ever beautiful string16s.
BUG=None
TEST=setup_util_unittests
installer_util_unittests --gtest_filter=InstallUtilTest.ProgramCompare
Review URL: https://chromiumcodereview.appspot.com/10446095
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@139837 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=
TEST=
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=139482
Review URL: https://chromiumcodereview.appspot.com/10458019
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@139828 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The flag was mostly redundant with the enable_touch_ui flag, the only
additional effect of turning it on was to change the behavior of
ui::GetDisplayLayout.
If we later wanted to duplicate the effect that disabling the
enable_metro flag prior to this change would have, we can simply
change the condition in common.gypi that determines whether to turn on
the enable_touch_ui flag.
BUG=none
Review URL: https://chromiumcodereview.appspot.com/10440037
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@139181 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
build is 8370 or higher.
This prevents us from launching Metro chrome on unsupported builds (launching from Start Screen simply defaults to desktop Chrome).
BUG=None
TEST=Chrome launches in Desktop from Start Screen on 8250 and to Metro in 8370.
Review URL: https://chromiumcodereview.appspot.com/10441012
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@138919 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These strings are also in the locale pak files, so this is a duplicate
of >250k of data. Add the ability to provide a different string
provider for BrowserDistribution.
BUG=128056
TEST=chrome --first-run still works
Review URL: https://chromiumcodereview.appspot.com/10386217
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@138859 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
user chrome.
BUG=138849
TEST=gcapi_example on a system with system keystone, but runnin gcapi_example as user.
Review URL: https://chromiumcodereview.appspot.com/10446020
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@138858 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Fix issues found by running it.
BUG=128462
TEST=Run this on machines without keystone and with keystone,
from a user account, and through sudo. Check the installed
chrome looks good, and that keystone gets installed if
necessary.
Review URL: https://chromiumcodereview.appspot.com/10446018
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@138849 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=128462
TEST=none
Review URL: https://chromiumcodereview.appspot.com/10407047
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@138813 0039d316-1c4b-4281-b951-d872f2087c98
|