| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
|
|
| |
- A typical configuration from real world.
- A configuration generated from CPanel.
BUG=162804
TBR=stevenjb@chromium.org
Review URL: https://chromiumcodereview.appspot.com/11488008
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@173460 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adapted NetworkLibrary and onc::CertificateImporter.
BUG=162801
TEST=Import an ONC with one invalid and one valid network/certificate.
Ensure that the valid one is correctly imported.
TBR=eroman@chromium.org (net_internals, string change)
Review URL: https://chromiumcodereview.appspot.com/11578005
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@173444 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=153004
For ash_strings.grd:
TBR=sky@chromium.org
Review URL: https://chromiumcodereview.appspot.com/11447025
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@173409 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Cleaned up ONC validator unit tests to scale better with more tests.
BUG=162801
TEST=Adapted the validator unit test.
Review URL: https://chromiumcodereview.appspot.com/11428078
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@173404 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adding also more validation tests.
The logging is in line with https://codereview.chromium.org/11299236/.
BUG=162802
TEST=Unit tests.
TBR=stevenjb@chromium.org,eroman@chromium.org (whitespace change in net_interals.cc)
Review URL: https://chromiumcodereview.appspot.com/11469026
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@173393 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Configure X server to use Coordinate Transformation Matrix
on touchscreen input devices for correct positioning of touch events.
This is useful for 2 cases:
1. Mirror mode with aspect preserving scaling,
which leaves blank areas on the screen,
touches in which will be scaled out.
2. Extended desktop mode,
in which a touchscreen occupies only a portion of the desktop,
and thus events coming from it need to be mapped into that portion.
This also requires changes in the analysis of a touch event -
instead of scaling it from desktop into RootWindow,
now it needs to be relocated into RootWindow's origin.
BUG=chrome-os-partner:16192
TEST=Attach a touchscreen to a Chromebook,
verify that touches are positioned correctly
in Extended Desktop and Mirror modes.
Review URL: https://chromiumcodereview.appspot.com/11416390
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@173316 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
calls from IBus.
BUG=164525
TEST=Try using Japanese IME and check the user log in chrome://system.
Review URL: https://chromiumcodereview.appspot.com/11570002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@173123 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adding 6 UMAs:
Display.GetDualOutputs.detected_mirror_mode is enumeration metric,
counting how many times the possibility of each mirror mode was detected:
aspect preserving, fallback, and impossible.
Display.EnterState.single_duration
Display.EnterState.mirror_aspect_duration
Display.EnterState.mirror_fallback_duration
Display.EnterState.dual_primary_duration
Display.EnterState.dual_secondary_duration
record how much time was spent in each of the states.
BUG=chrome-os-partner:16384
TEST=Connect external display, enter-exit mirror mode, see about:histograms.
Review URL: https://chromiumcodereview.appspot.com/11519002
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@172763 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
so that it can be used there without violating dependency
rules.
(Using the "refactoring" OWNERS TBR rule...)
BUG=none
TEST=ran unit tests
TBR=jhawkins@chromium.org
Review URL: https://chromiumcodereview.appspot.com/11299236
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@172446 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=161869
For chrome/browser/ui/webui/options/chromeos
TBR=nkostylev@chromium.org
Review URL: https://codereview.chromium.org/11428158
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@172156 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When configuring outputs, don't reallocate the framebuffer if it's already the
right size. This avoids the ConfigureCrtc calls which turn off all the
displays. This reconfiguration can take up to two seconds on Link, because
each panel on/off takes 500ms there.
This speeds up modesetting, and suspend/resume times. Note that this applies
to all Chrome OS machines, so will result in improving times across the board,
but the panel timings aren't as bad on other platforms so it makes less of a
difference.
BUG=chrome-os-partner:13364
TEST=by hand
Change-Id: Ia8344aa689c0307e8a1c85a5a2b75af6fb4b8371
Review URL: https://chromiumcodereview.appspot.com/11471039
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@171999 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, the resolution chosen for mirror mode would be
the highest common resolution among the internal and external displays.
This would often fall back to the 1024x768 case,
which looks bad on wide displays and internal panels.
Now, external display resolutions with display's native aspect ratio
will be considered first for mirror mode,
trying to create a matching internal display resolution using panel fitting,
when possible, if one doesn't exist already.
For that sake, this commit also enables panel fitting on SNB.
In case of 2 external monitors, mirror mode will first try to find
a common resolution which will preserve aspect ratio on at least one of them.
If an aspect ratio preserving resolution has not been found,
fall back to the existing solution of highest common resolution.
BUG=chrome-os-partner:16384
TEST=For the displays in bug report, mirror mode resolution is 1280x720.
Review URL: https://chromiumcodereview.appspot.com/11411304
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@171877 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
| |
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@171825 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
http://build.chromium.org/p/chromium.chromiumos/buildstatus?builder=Linux%20ChromiumOS%20%28Clang%20dbg%29&number=25562
> Force mirror mode to preserve aspect ratio, use panel fitting when possible.
>
> Previously, the resolution chosen for mirror mode would be
> the highest common resolution among the internal and external displays.
> This would often fall back to the 1024x768 case,
> which looks bad on wide displays and internal panels.
>
> Now, only external display resolutions with display's native aspect ratio
> will be considered for mirror mode.
>
> This will often end up in "can't mirror",
> so this commit also enables panel fitting on SNB,
> which will try to panel fit external display's resolution on internal panel,
> even if the panel didn't advertise support for this resolution.
>
> In case of 2 external monitors, mirror mode will try to find
> a common resolution which will preserve aspect ratio on at least one of them.
>
> For now, panel fitting is used only on internal panels.
> In the future it may be feasible to support it on external displays as well,
> which will allow us to always enter mirror mode,
> providing that GPU has panel fitter.
>
> BUG=chrome-os-partner:16384
> TEST=For the displays in bug report, mirror mode resolution is 1280x720.
>
>
> Review URL: https://chromiumcodereview.appspot.com/11411304
TBR=ynovikov@chromium.org
Review URL: https://codereview.chromium.org/11474020
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@171750 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, the resolution chosen for mirror mode would be
the highest common resolution among the internal and external displays.
This would often fall back to the 1024x768 case,
which looks bad on wide displays and internal panels.
Now, only external display resolutions with display's native aspect ratio
will be considered for mirror mode.
This will often end up in "can't mirror",
so this commit also enables panel fitting on SNB,
which will try to panel fit external display's resolution on internal panel,
even if the panel didn't advertise support for this resolution.
In case of 2 external monitors, mirror mode will try to find
a common resolution which will preserve aspect ratio on at least one of them.
For now, panel fitting is used only on internal panels.
In the future it may be feasible to support it on external displays as well,
which will allow us to always enter mirror mode,
providing that GPU has panel fitter.
BUG=chrome-os-partner:16384
TEST=For the displays in bug report, mirror mode resolution is 1280x720.
Review URL: https://chromiumcodereview.appspot.com/11411304
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@171737 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
This CL is a two-line fix for r171702. I had updated that CL locally but
accidentally committed an older version.
BUG=36892
TBR=bartfab@chromium.org
Review URL: https://codereview.chromium.org/11478020
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@171734 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This CL adds a flag that allows Chrome to request an ephemeral mount for
a user. If the flag is set, a cryptohome backed by tmpfs will always be
mounted, even if a regular vault exists for the user.
This functionality is required for public accounts that look like regular
accounts to cryptohomed otherwise but whose cryptohomes must always be
ephemeral.
The CL is a companion to https://gerrit.chromium.org/gerrit/#/c/38995/ on
the cryptohomed side.
BUG=chromium-os:36892
Review URL: https://chromiumcodereview.appspot.com/11444006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@171702 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is the last CL for libibus removal.
We can also remove InputMethodLookupTable and IBusUiController as well, but let me split cl for them.
BUG=158264, 158265
TEST=Manually done on lumpy.
Review URL: https://chromiumcodereview.appspot.com/11280159
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170790 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the case of Japanese, IME shows word usage or its description. This
feature is already supported in Chrome OS native ibus IME engines.
With this patch, Chrome supports same feature for Extension IME.
This change does not affect existing extension implementation in terms of
backward compatibility.
BUG=158486
TEST=manually done one lumpy.
Review URL: https://chromiumcodereview.appspot.com/11412268
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170670 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Most of connection management stuff is moved to chromeos/dbus/ibus/ibus_config_client
This CL depends https://codereview.chromium.org/11413165/
BUG=158265
TEST=Manually done on lumpy
Review URL: https://chromiumcodereview.appspot.com/11419202
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170651 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=163111
TEST=ran chromeos_unittests
Review URL: https://chromiumcodereview.appspot.com/11416243
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170490 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
IBusConfigClient can not always initialize synchronously, because there is a case that the ibus-config daemon is not running.
BUG=158265
TEST=ran chromeos_unittests
Review URL: https://chromiumcodereview.appspot.com/11413165
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170432 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=154104
Review URL: https://chromiumcodereview.appspot.com/11419231
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170377 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
CashewClient has been deprecated and should be removed.
BUG=162717
Review URL: https://codereview.chromium.org/11299246
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@170210 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
Also adds verbose(2) logging to network_event_log
BUG=none
Review URL: https://chromiumcodereview.appspot.com/11280199
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@169942 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
The reason why I introduced two different interfaces is that CandidateWindow and Property controllers are separated in Chrome.
CandidateWindowHandler is(will be) implemented by CandidateWindowController and PropertyHandler is(will be) implemented by IBusController.
BUG=158265
TEST=ran chromeos_unittests
Review URL: https://chromiumcodereview.appspot.com/11416172
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@169904 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=146981
TEST=compile, open Drive on Files.app, and open and copy a file in Drive. "Drive*" and "GData" in unit_test and browser_tests pass.
Review URL: https://chromiumcodereview.appspot.com/11414152
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@169868 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
BUG=none
Review URL: https://codereview.chromium.org/11413176
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@169610 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
This is just a bit of cleanup I did while working in data plans support.
BUG=none
Review URL: https://chromiumcodereview.appspot.com/11417128
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@169544 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
This does some cleanup to allow NetworkStateHandler to use the same error callback infrastructure as NetworkConfigurationHandler.
It also adds event logging for errors.
BUG=none
Review URL: https://codereview.chromium.org/11416149
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@169475 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
This cl depends on https://codereview.chromium.org/11411063
BUG=140186
TEST=Manually done on lumpy with sample IME.
Review URL: https://chromiumcodereview.appspot.com/11299104
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@169414 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This makes Chrome observe the SuspendStateChanged D-Bus
signal that powerm now emits when we're suspending or
resuming. The old signal from powerd_suspend stopped
working since it was being sent by an unauthorized client.
BUG=chromium-os:36503
TEST=clock updates immediately after resuming
Review URL: https://codereview.chromium.org/11421046
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@169404 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds a RootPowerManagerClient class for communicating
over D-Bus with the powerm process. I'm also updating
Chrome to use the power button events from powerm instead of
the ones from powerd.
BUG=chromium-os:36380,chromium-os:36503
Review URL: https://chromiumcodereview.appspot.com/11421023
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@169089 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=161294
TEST=DiskMountManagerTest* under valgrind/heapcheck
Review URL: https://chromiumcodereview.appspot.com/11416017
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@169049 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=chromium-os:35715
TEST=None
Review URL: https://chromiumcodereview.appspot.com/11416098
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@169040 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This also extracts about_network from about_ui for the chrome://network UI, updating it for NetworkState and NetworkEventLog.
Additionally network event logs (and a dbus summary) are added to feedback reports)
BUG=161369
For chrome/browser/ui/webui/:
TBR=jhawkins@chromium.org
Review URL: https://chromiumcodereview.appspot.com/11416041
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@168946 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
against the testserver.
BUG=108928
Review URL: https://chromiumcodereview.appspot.com/11414007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@168807 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
| |
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@168736 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the case of power state override being created and immidiatelly destructed, we'll have a scenario in which the correct power state request won't get cancelled.
e.g.,
. User creates PowerStateOverride instance -> We call RequestPowerStateOverride
- we wait for the callback from ChromeOS to get our request ID
. User deletes PowerStateOverride instance -> We call CancelPowerStateOverride with a 0 request ID
. We destruct, invalidating our weak pointers
. Callback from RequestPowerStateOverride never lands since the weakptr is invalidated
- Power state override remains in effect for the next 10 minutes.
This has now changed to,
. User creates PowerStateOverride instance -> We call RequestPowerStateOverride, this increments our reference count to 2
- we wait for the callback from ChromeOS to get our request ID
. User releases his refernce to PowerStateOverride instance -> We decrement our reference count to 1
. RequestPowerStateOverride returns, giving us our RequestID, and decrements our refernce count to 0
. Destructor gets called, which does a CancelPowerStateOverride with the correct request ID
- The PowerStateOverride is cancelled
R=derat@chromium.org
BUG=151732
Review URL: https://codereview.chromium.org/11358222
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@168644 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=none
Review URL: https://chromiumcodereview.appspot.com/11308103
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@168572 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=chromium-os:35715
TEST=None
Review URL: https://chromiumcodereview.appspot.com/11360191
You had a green linux_chromeos try run, but unfortunately, clang is pickier:
http://build.chromium.org/p/chromium.chromiumos/builders/Linux%20ChromiumOS%20%28Clang%20dbg%29/builds/24522
TBR=mnissler@chromium.org
Review URL: https://codereview.chromium.org/11308106
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@168567 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=chromium-os:35715
TEST=None
Review URL: https://chromiumcodereview.appspot.com/11360191
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@168563 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Sorry I misunderstand the infolist spec, infolist requires title field.
I split description field into description_title and description_body.
BUG=129403
TEST=ran chromeos_unittests
Review URL: https://chromiumcodereview.appspot.com/11362111
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@168544 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
With this CL, IBusObjectReader/IBusObjectWriter can read/write attachment field in IBusObject header field.
BUG=140186
TEST=ran chromeos_unittests
Review URL: https://chromiumcodereview.appspot.com/11361210
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@168522 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Revert r168420 "chromeos/power: Refcounted types should not have public destructors."
Broke linux_chromeos_clang.
TBR=tfarina@chromium.org,derat@chromium.org,rkc@chromium.org
BUG=123295
Review URL: https://codereview.chromium.org/11415041
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@168421 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
This was broken this CL: https://chromiumcodereview.appspot.com/11358222/
BUG=123295
TBR=derat@chromium.org,rkc@chromium.org
Review URL: https://codereview.chromium.org/11413056
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@168420 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
In the case of power state override being created and immidiatelly destructed, we'll have a scenario in which the correct power state request won't get cancelled.
e.g.,
. User creates PowerStateOverride instance -> We call RequestPowerStateOverride
- we wait for the callback from ChromeOS to get our request ID
. User deletes PowerStateOverride instance -> We call CancelPowerStateOverride with a 0 request ID
. We destruct, invalidating our weak pointers
. Callback from RequestPowerStateOverride never lands since the weakptr is invalidated
- Power state override remains in effect for the next 10 minutes.
This has now changed to,
. User creates PowerStateOverride instance -> We call RequestPowerStateOverride, this increments our reference count to 2
- we wait for the callback from ChromeOS to get our request ID
. User releases his refernce to PowerStateOverride instance -> We decrement our reference count to 1
. RequestPowerStateOverride returns, giving us our RequestID, and decrements our refernce count to 0
. Destructor gets called, which does a CancelPowerStateOverride with the correct request ID
- The PowerStateOverride is cancelled
R=derat@chromium.org
BUG=151732
Review URL: https://chromiumcodereview.appspot.com/11358222
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@168414 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
that will eventually replace the NetworkLibrary method
of configuring networks.
BUG=none
TEST=none
Review URL: https://chromiumcodereview.appspot.com/11260047
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@168338 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Adds static Initialize() and Shutdown() metgods for NetworkStateHandler.
BUG=none
For about_flags:
TBR=ben@chromium.org
Review URL: https://codereview.chromium.org/11316032
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@168232 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
We were formerly getting notified via D-Bus signal from the
power manager whenever the lock key on external Chrome OS
keyboards (F13) was pressed or released. This change makes
Chrome instead listen for F13 directly, which will allow
apps to override the F13 key when desired.
BUG=153951
TEST=lock key still works as before
Review URL: https://chromiumcodereview.appspot.com/11420009
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@168022 0039d316-1c4b-4281-b951-d872f2087c98
|