| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=110127
BUG=chromium-os:26033
TEST=manual
Review URL: http://codereview.chromium.org/9475005
TBR=dmazzoni@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9845025
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@128529 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
enabled (non-Aura).
(Needs to be manually merged, will re-land.)
BUG=110127
BUG=chromium-os:26033
TEST=manual
Review URL: http://codereview.chromium.org/9475005
TBR=dmazzoni@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9839062
TBR=ddrew@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9839063
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@128528 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=110127
BUG=chromium-os:26033
TEST=manual
Review URL: http://codereview.chromium.org/9475005
TBR=dmazzoni@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9839062
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@128521 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
extension permissions.
This also updates the following permissions to use the whitelist:
- terminalPrivate
- webSocketProxyPrivate
- chromePrivate
- inputMethodPrivate
- chromeAuthPrivate
- webstorePrivate
Includes more tests to verify that Extension loading fails for different permission parameters:
- by extension type
- component only flag
- whitelists
BUG=84211, 111314
TEST=extension unit and browser tests
Review URL: http://codereview.chromium.org/9317013
TBR=jstritar@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9703090
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@127007 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
to sign-in.
This was caused by fetching a device policy during enrollment that causes a
refresh of the sign-in screen. However, that refresh would also hide the
enrollment screen and go back to sign-in at the wrong time.
BUG=chromium-os:27038
TEST=Enroll a device with the show_user_names policy set to false. The enrollment successful screen should wait for the user to click Done before proceeding.
Review URL: http://codereview.chromium.org/9592024
TBR=joaodasilva@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9693021
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@126249 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Disabled until we have a sufficient notification to the user that
device activity time is being recorded & reported.
BUG=chromium-os:26251
TEST=Manual.
Review URL: http://codereview.chromium.org/9388005
TBR=mnissler@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9572026
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@124796 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
already enrolled.
This should never happen (ha!), but if it does then this fix prevents the
never ending "in progress" spinner.
BUG=chromium-os:26780
TEST=The steps described in the bug report don't enter a never ending spinner, and an error is shown instead.
Review URL: http://codereview.chromium.org/9455058
TBR=joaodasilva@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9555003
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@124268 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=chromium-os:26780
TEST=Follow the steps from the bug report. The 2nd sign-in doesn't try to enroll again, and doesn't get stuck.
Review URL: http://codereview.chromium.org/9460008
TBR=joaodasilva@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9549006
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@124267 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
doesn't change the password.
BUG=chromium-os:26928
TEST=manual
Review URL: https://chromiumcodereview.appspot.com/9477007
TBR=chocobo@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9535023
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@124232 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
network dropdown menu.
BUG=chromium-os:25163
TEST=manual
Review URL: https://chromiumcodereview.appspot.com/9466018
TBR=chocobo@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9536021
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@124231 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The problem happened because the page used chrome:// to load local_strings.js but it failed because page itself is served from data URL that has no access to chrome://. Error in the log was "Not allowed to load local resource". Now local_strings.js is flatten and it fixes the issue. Also return timeout for showing offline error page.
BUG=chromium-os:23792
TEST=manual
Review URL: http://codereview.chromium.org/9427008
TBR=dpolukhin@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9537002
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@124135 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
chromeos::Brightness/Resume/ScreenLockObserver
These observers must be initialized after the default profile.
BUG=chromium-os:26852
TEST=Press brightness change key and see brightness change notification bubble appears.
Review URL: http://codereview.chromium.org/9494002
TBR=hashimoto@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9500006
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@124121 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
enabled (non-Aura).
BUG=110127
BUG=chromium-os:26033
TEST=manual
Review URL: http://codereview.chromium.org/9475005
TBR=dmazzoni@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9514019
TBR=dmazzoni@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9513017
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@124074 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=110127
BUG=chromium-os:26033
TEST=manual
Review URL: http://codereview.chromium.org/9475005
TBR=dmazzoni@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9514019
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@124051 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This allows us to disable features in branches.
BUG=chromium-os:26137
TEST=Emerged chrome locally on lumpy.
Review URL: http://codereview.chromium.org/9461001
TBR=ihf@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9517009
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@124050 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Don't ever delete existing certs if not explicitly requested, since
these might also be required by other ONC blobs and/or SSL. Furthermore,
work around an issue in case the cert bits already exist in NSS: In that
case we cannot create a temporary cert, but need to delete the existing
one and recreate the temp cert and import afterwards to update the
nickname.
BUG=chromium-os:23478
TEST=Re-importing ONC policy doesn't run into duplicate cert errors.
Review URL: https://chromiumcodereview.appspot.com/9474031
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@123839 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=chromium-os:23751
TEST=unit test
Review URL: http://codereview.chromium.org/9234032
TBR=mnissler@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9425044
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@122741 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Bug was that when error page is gone so is proxy dialog delegate.
BUG=chromium-os:26315
TEST=Go through OOBE on network that requires proxy. From sign in screen error page open proxy settings (not from the top right menu). Wait for GAIA frame reload (see logs) and close dialog. No crash.
Review URL: http://codereview.chromium.org/9405008
TBR=nkostylev@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9427006
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@122735 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=chromium-os:26001
TEST=manual
Review URL: http://codereview.chromium.org/9372019
TBR=dpolukhin@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9427003
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@122729 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
http://chromiumcodereview.appspot.com/9406003/
For VPN passwords that are not passed back to the UI from flimflam, we show a fake password ******** in the UI. When user focuses on the textfield, we clear it out and replace it when the textfield loses focus and the user has not changed the password.
BUG=chromium-os:24685
TEST=manual
Review URL: https://chromiumcodereview.appspot.com/9416036
TBR=chocobo@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9355019
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@122589 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Change-Id: I251481f0feb3f782f34213b5dc731847b7e42ae9
BUG=chromium-os:24836
TEST=Ensure login times are not any slower and that UI for connecting to a network with a certificate works and does not stall. Also ensure crash in issue stops showing up.
Review URL: http://codereview.chromium.org/9323048
TBR=stevenjb@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9402020
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@122127 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=chromium-os:26119
TEST=Open chrome://imageburner, press Ctrl+Shift+Q to quit, see the content of the log for the last session (can find in /var/log/ui/) and ensure there is no crash.
Review URL: http://codereview.chromium.org/9373020
TBR=hashimoto@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9348077
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@121854 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
A crash on IO thread could happen when signing out with pending LoginUtils
background jobs. The crash happens because user profile and its network
delegate is already released when we try to cancel the background jobs. This CL
fixes the issue by explicitly stopping those background fetchers.
BUG=chromium-os:26138
TEST=Verify the crash part not happening in chromium-os:23138
Review URL: http://codereview.chromium.org/9389017
TBR=zelidrag@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9350068
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@121828 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Change-Id: I30a727034867f017008b2f24956120ecb8d08aca
BUG=23948
TEST=See issue
Review URL: http://codereview.chromium.org/9375034
TBR=stevenjb@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9383014
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@121534 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
new user flow.
BUG=112225
TEST=Log in as a new user. Close the lid and verify that after a few seconds opening again you are logged out.
Review URL: https://chromiumcodereview.appspot.com/9349022
TBR=flackr@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9373040
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@121307 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=110943
TEST=no crash
Review URL: http://codereview.chromium.org/9348061
TBR=varunjain@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9369016
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@121162 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
if available.
Previously we would only re-encrypt an account that had implicit passphrases if,
on a password change, the client was already signed in. Otherwise, for example
if the user signs in to a new client, we would disregard the current credentials
because they are unable to decrypt the existing encrypted data (based on the old
gaia password).
This change ensures we do not throw away the old credentials. If we have pending
keys, we go ahead and generate new encryption keys based on the new credentials
and set those keys as the default. In addition, we persist the keys in the
bootstrap token for the cryptographer. In this way, the bootstrap token for
accounts using implicit passphrases will always correspond to the encryption
keys derived from the most recent gaia password.
Once the user supplies the old gaia password (which they will be prompted for
due to the cryptographer having pending keys), we will install it, but then
restore the encryption keys based on the current gaia password as the default.
This decision is made based on whether the pending keybag contains the current
default key or not. If it does, then the keybag must be newer than our data,
and we let it overwrite the default. If it does not, then our current key
is the newest, and we persist the current default.
In order to support this change, we plumb from the setup flow whether a
passphrase originates from the user or from an internal source (the
signin successful notification). In this way we can differentiate the current
implicit passphrase from an older user provided one.
BUG=104508
TEST=sync_unit_tests. All existing passphrase tests. Manually signing into
a clean account, setting up sync, signing out, changing the password, then
signing in to a new client. The new client should prompt for the old password,
but once provided should re-encrypt all data with the new password.
Subsequent new clients should not prompt for any old password.
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=120157
Review URL: https://chromiumcodereview.appspot.com/9309022
TBR=zea@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9365038
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@121053 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
newest gaia password if available.
Previously we would only re-encrypt an account that had implicit passphrases if,
on a password change, the client was already signed in. Otherwise, for example
if the user signs in to a new client, we would disregard the current credentials
because they are unable to decrypt the existing encrypted data (based on the old
gaia password).
This change ensures we do not throw away the old credentials. If we have pending
keys, we go ahead and generate new encryption keys based on the new credentials
and set those keys as the default. In addition, we persist the keys in the
bootstrap token for the cryptographer. In this way, the bootstrap token for
accounts using implicit passphrases will always correspond to the encryption
keys derived from the most recent gaia password.
Once the user supplies the old gaia password (which they will be prompted for
due to the cryptographer having pending keys), we will install it, but then
restore the encryption keys based on the current gaia password as the default.
This decision is made based on whether the pending keybag contains the current
default key or not. If it does, then the keybag must be newer than our data,
and we let it overwrite the default. If it does not, then our current key
is the newest, and we persist the current default.
In order to support this change, we plumb from the setup flow whether a
passphrase originates from the user or from an internal source (the
signin successful notification). In this way we can differentiate the current
implicit passphrase from an older user provided one.
BUG=104508
TEST=sync_unit_tests. All existing passphrase tests. Manually signing into
a clean account, setting up sync, signing out, changing the password, then
signing in to a new client. The new client should prompt for the old password,
but once provided should re-encrypt all data with the new password.
Subsequent new clients should not prompt for any old password.
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=120157
Review URL: https://chromiumcodereview.appspot.com/9309022
TBR=zea@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9367001
TBR=zea@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9360026
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@121037 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
if available.
Previously we would only re-encrypt an account that had implicit passphrases if,
on a password change, the client was already signed in. Otherwise, for example
if the user signs in to a new client, we would disregard the current credentials
because they are unable to decrypt the existing encrypted data (based on the old
gaia password).
This change ensures we do not throw away the old credentials. If we have pending
keys, we go ahead and generate new encryption keys based on the new credentials
and set those keys as the default. In addition, we persist the keys in the
bootstrap token for the cryptographer. In this way, the bootstrap token for
accounts using implicit passphrases will always correspond to the encryption
keys derived from the most recent gaia password.
Once the user supplies the old gaia password (which they will be prompted for
due to the cryptographer having pending keys), we will install it, but then
restore the encryption keys based on the current gaia password as the default.
This decision is made based on whether the pending keybag contains the current
default key or not. If it does, then the keybag must be newer than our data,
and we let it overwrite the default. If it does not, then our current key
is the newest, and we persist the current default.
In order to support this change, we plumb from the setup flow whether a
passphrase originates from the user or from an internal source (the
signin successful notification). In this way we can differentiate the current
implicit passphrase from an older user provided one.
BUG=104508
TEST=sync_unit_tests. All existing passphrase tests. Manually signing into
a clean account, setting up sync, signing out, changing the password, then
signing in to a new client. The new client should prompt for the old password,
but once provided should re-encrypt all data with the new password.
Subsequent new clients should not prompt for any old password.
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=120157
Review URL: https://chromiumcodereview.appspot.com/9309022
TBR=zea@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9367001
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@121030 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
change.
If pasword change is detected, user is redirected to GAIA login flow. Also note about password change is shown.
BUG=chromium-os:24984
TEST=manual
Review URL: http://codereview.chromium.org/9225044
TBR=altimofeev@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9345001
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@120616 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
On restarting from a crashed chrome, authenticator_ is NULL and causing
more crashes in FetchPolicyToken.
BUG=chromium-os:25865
TEST=Verify fix for chromium-os:25865.
Review URL: http://codereview.chromium.org/9309096
TBR=zelidrag@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9333006
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@120579 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
and is restarted.
BUG=112109
TEST=Crash the browser and verify that screenlocker observers have been registered (i.e. short power press works).
Review URL: https://chromiumcodereview.appspot.com/9310002
TBR=flackr@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9317057
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@120228 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is check-in for mattias.
Original review: http://codereview.chromium.org/9315011/
Note that this hard-wires policy OAuth fetching in login_utils.cc to the
authentication profile. I'm not entirely sure this is a good idea, but
required since the user profile isn't in a state to allow successful
requests at this point (the use-shared-proxies flag is off). Other stuff
in login_utils.cc might need the hack too (sync?).
BUG=chromium-os:25703
TEST=Verify fix for chromium-os:25703
TBR=mnissler@chromium.org,zelidrag@chromium.org,sumit@chromium.org,pastarmovj@chromium.org,kuan@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9309024
TBR=xiyuan@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9309053
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@120203 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
populate the use_shared_proxies pref.
This is necessary to enforce proper operation if the browser crashes too
early in the login sequence and the preferences file has not been stored
yet.
BUG=chromium-os:25703
TEST=Manually tested by putting a DCHECK just after setting the pref in LoginUtilsImpl::OnProfileCreated.
Review URL: https://chromiumcodereview.appspot.com/9314031
TBR=pastarmovj@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9317050
git-svn-id: svn://svn.chromium.org/chrome/branches/1025/src@120202 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
chromeos/power looks more suitable place for the code than chromeos/system
BUG=None
TEST=Turn on spoken feedback and ensure audio feedbacks are made when resuming from suspend or unlocking screen.
Review URL: http://codereview.chromium.org/9234060
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@119867 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=None
TEST=chrome://imageburner works
Review URL: http://codereview.chromium.org/9225054
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@119866 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
BUG=chromium-os:23673
TEST=OncNetworkParserTest
Review URL: https://chromiumcodereview.appspot.com/9297061
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@119799 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
The lock screen container needs a layout manager to respond to resolution changes caused by an external monitor being attached or detached. Marking the login screen widget as fullscreen makes it reshape to track the size change.
BUG=110942
TEST=manual
Review URL: https://chromiumcodereview.appspot.com/9121063
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@119732 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, the UI would make decision based on the enabled() state of
controls, indicating that the control is not relevant for the currently
chosen configuration. This doesn't work for policy-configured networks,
since the control might just be locked down, in which case it is
relevant, but disabled.
BUG=chromium-os:23124
TEST=Configure ONC networks through policy, observe that the connection dialogs show the configured values even though disabled.
Review URL: https://chromiumcodereview.appspot.com/9296009
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@119664 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=108740
TEST=Manul: see bug description.
Review URL: https://chromiumcodereview.appspot.com/9113080
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@119653 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
burn_controller.cc
BUG=chromium-os:16553
TEST=chrome://imageburner works
Review URL: https://chromiumcodereview.appspot.com/9235028
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@119651 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Revert 119620 - Revert r119614 "Make auto-enrollment client retry after auto-update if the modulus limit was in..."
I initially thought r119615 was the culprit but I was wrong. Only r119614 could
now possibly make ExtensionApiTest.ProcessesVsTaskManager time out reliably on
windows.
TBR=joaodasilva@chromium.org
BUG=
TEST=
Review URL: https://chromiumcodereview.appspot.com/9295039
TBR=maruel@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9296037
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@119629 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
modulus limit was in..."
I initially thought r119615 was the culprit but I was wrong. Only r119614 could
now possibly make ExtensionApiTest.ProcessesVsTaskManager time out reliably on
windows.
TBR=joaodasilva@chromium.org
BUG=
TEST=
Review URL: https://chromiumcodereview.appspot.com/9295039
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@119620 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
increased.
Also moved the local state handling code to auto_enrollment_client.cc.
BUG=chromium-os:23063
TEST=AutoEnrollmentClientTest.*
Review URL: http://codereview.chromium.org/9296007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@119614 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
prevents the browser window from receiving focus.
Removed current fade out animation in favor of ash's hide animation. Ash hide animation will be added once ben's hide animation refactoring is done.
BUG=101119
TEST=manual: see bug for repro step
Review URL: http://codereview.chromium.org/9290019
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@119560 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
For example, if the current tab is navigated to a JPEG and the user chooses "Save Page As" from the wrench menu, the data will be retrieved from cache without validation even if Cache-Control: no-cache is specified.
BUG=32246,55551,94574
TEST=DownloadTest.SavePageNonHTMLViaGet
Review URL: http://codereview.chromium.org/9178029
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@119538 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Change-Id: Ide0e496c6919282ee707847c4d11db8a182eeac2
BUG=24403
TEST=Add a certificate. Ensure that it shows up when adding Wifi or VPN networks. Remove the certificate. Make sure it is no longer available when adding Wifi or VPN networks. Also, see issue.
Review URL: http://codereview.chromium.org/9280014
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@119536 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
[part 2 of 2].
Add caps_lock_handler.cc which implements ash::CapsLockDelegate.
Part 1 of 2: http://codereview.chromium.org/9242003
Original review for Part 2 of 2: http://codereview.chromium.org/9225004/ (LGTM'ed by ben@chromium.org and derat@chromium.org)
BUG=110129
TEST=ran browser_tests
TBR=ben@chromium.org,derat@chromium.org
Review URL: https://chromiumcodereview.appspot.com/9297027
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@119513 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=110765
TEST=Lock the screen, open network menu, select proxy settings. Observe proxy settings dialog.
Review URL: https://chromiumcodereview.appspot.com/9296013
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@119500 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is mostly everything except code under /sync or sync_internals (those require a little more time
as they have unit test implications). The ones here are quite simple but need several owner-approvals, and given the upcoming 18 branch I'd like
to get this landed without a cross-team monday crunch :)
TBR=jhawkins@chromium.org
TBR=mirandac@chromium.org
TBR=isherman@chromium.org
TBR=nkostylev@chromium.org
TBR=estade@chromium.org
BUG=93922
Review URL: http://codereview.chromium.org/9169096
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@119482 0039d316-1c4b-4281-b951-d872f2087c98
|