| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
|
| |
BUG=115047
TBR=satorux@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10910131
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@155432 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=none
TEST=none
Review URL: https://chromiumcodereview.appspot.com/10917115
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@155319 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=139266
TEST=manual
Review URL: https://chromiumcodereview.appspot.com/10915055
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@155313 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
http://build.chromium.org/p/chromium/builders/Win%20Aura/builds/21280/steps/ash_unittests/logs/stdio#failure1
[ RUN ] VideoDetectorTest.FullscreenWindow
wm\video_detector_unittest.cc(250): error: Value of:
observer_->num_invocations()
Actual: 0
Expected: 1
wm\video_detector_unittest.cc(251): error: Value of:
observer_->num_fullscreens()
Actual: 0
Expected: 1
[ FAILED ] VideoDetectorTest.FullscreenWindow (138 ms)
This is a re-attempt at http://codereview.chromium.org/10905026/, which ended up
being reverted.
The crash that caused the revert was actually due to powerd not being able to
parse the protobuf correctly. https://gerrit.chromium.org/gerrit/32243/ corrects
this issue, so once that CL lands this CL is good to go. I confirmed the
combination of CLs works correctly.
This is the original CL description:
This adds a boolean to the video update message sent to powerd that indicates
whether or not the video playing window is fullscreen'd. This is information
used in powerd for controlling when to enable/disable keyboard
backlights. Specifically if video is playing and fullscreen we assume that the
user is doing something like watching a movie so will disable backlight.
An additional change that I have made is to convert the message being sent from
an int64 to a protobuffer that contains a int64 and a boolean. Currently, since
the receiver of this message does not live in the same repo it means that
everytime one wants to change the message format there is a small window where
bad builds can be generated or one has to land two changes to the other repo,
one to add handling of the new message format and then a second one to remove
the old format. Converting to a protobuffer means that for common cases this
issues are removed.
This CL depends on CLs for power_manager
(https://gerrit.chromium.org/gerrit/32092/), one for system_api
(https://gerrit.chromium.org/gerrit/31916), and a DEPS
roll(http://codereview.chromium.org/10915032/). There will be future CLs for
power_manager that will use this information and more thourghly tests this code.
BUG=chrome-os-partner:9203
TEST=Run updated unittests.
Confirm there is no messages in the cros logs about this method being
mishandled.
Make sure that powerd is not crashing due to protocol buffer processing
failing.
Review URL: https://chromiumcodereview.appspot.com/10916123
TBR=rharrison@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10928037
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@155232 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
annotations.
BUG=115047
TBR=satorux@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10918100
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@155230 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a re-attempt at http://codereview.chromium.org/10905026/, which ended up
being reverted.
The crash that caused the revert was actually due to powerd not being able to
parse the protobuf correctly. https://gerrit.chromium.org/gerrit/32243/ corrects
this issue, so once that CL lands this CL is good to go. I confirmed the
combination of CLs works correctly.
This is the original CL description:
This adds a boolean to the video update message sent to powerd that indicates
whether or not the video playing window is fullscreen'd. This is information
used in powerd for controlling when to enable/disable keyboard
backlights. Specifically if video is playing and fullscreen we assume that the
user is doing something like watching a movie so will disable backlight.
An additional change that I have made is to convert the message being sent from
an int64 to a protobuffer that contains a int64 and a boolean. Currently, since
the receiver of this message does not live in the same repo it means that
everytime one wants to change the message format there is a small window where
bad builds can be generated or one has to land two changes to the other repo,
one to add handling of the new message format and then a second one to remove
the old format. Converting to a protobuffer means that for common cases this
issues are removed.
This CL depends on CLs for power_manager
(https://gerrit.chromium.org/gerrit/32092/), one for system_api
(https://gerrit.chromium.org/gerrit/31916), and a DEPS
roll(http://codereview.chromium.org/10915032/). There will be future CLs for
power_manager that will use this information and more thourghly tests this code.
BUG=chrome-os-partner:9203
TEST=Run updated unittests.
Confirm there is no messages in the cros logs about this method being
mishandled.
Make sure that powerd is not crashing due to protocol buffer processing
failing.
Review URL: https://chromiumcodereview.appspot.com/10916123
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@155224 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Since the multi-monitor support code was first implemented back in powerd, we
have always had rare and unrecreatable bugs where we see inconsistent XRandR
data. The prime suspect of this problem is our reliance on the XRandR cache
which has existed in some form since the earliest versions of this code and
has always had the potential problem of allowing XRandR data to escape the
lifespan of the event being processed.
Additionally, bugs are periodically introduced due to needing to keep this cache
in sync with the underlying X server process.
By making OutputConfigurator stateless, the potential of a stale or otherwise
inconsistent cache disappears.
BUG=chromium:142860
TEST=Manually tested on Lumpy: add/remove second display, cycle displays,
manually power down and up the internal panel.
Review URL: https://chromiumcodereview.appspot.com/10907078
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@155211 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Breaks cros_x86, cros_amd64 buildbots:
http://build.chromium.org/p/chromium.chromiumos/builders/ChromiumOS%20%28x86%29/builds/8115
This adds a boolean to the video update message sent to powerd that indicates whether or not the video playing window is fullscreen'd. This is information used in powerd for controlling when to enable/disable keyboard backlights. Specifically if video is playing and fullscreen we assume that the user is doing something like watching a movie so will disable backlight.
An additional change that I have made is to convert the message being sent from an int64 to a protobuffer that contains a int64 and a boolean. Currently, since the receiver of this message does not live in the same repo it means that every time one wants to change the message format there is a small window where bad builds can be generated or one has to land two changes to the other repo, one to add handling of the new message format and then a second one to remove the old format. Converting to a protobuffer means that for common cases this issues are removed.
This CL depends on CLs for power_manager (https://gerrit.chromium.org/gerrit/32092/), one for system_api (https://gerrit.chromium.org/gerrit/31916), and a DEPS roll(http://codereview.chromium.org/10915032/). There will be future CLs for power_manager that will use this information and test this code.
BUG=chrome-os-partner:9203
TEST=Run updated unittests.
Confirm there is no messages in the cros logs about this method being mishandled.
Review URL: https://chromiumcodereview.appspot.com/10905026
TBR=rharrison@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10915089
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@154952 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This adds a boolean to the video update message sent to powerd that indicates whether or not the video playing window is fullscreen'd. This is information used in powerd for controlling when to enable/disable keyboard backlights. Specifically if video is playing and fullscreen we assume that the user is doing something like watching a movie so will disable backlight.
An additional change that I have made is to convert the message being sent from an int64 to a protobuffer that contains a int64 and a boolean. Currently, since the receiver of this message does not live in the same repo it means that every time one wants to change the message format there is a small window where bad builds can be generated or one has to land two changes to the other repo, one to add handling of the new message format and then a second one to remove the old format. Converting to a protobuffer means that for common cases this issues are removed.
This CL depends on CLs for power_manager (https://gerrit.chromium.org/gerrit/32092/), one for system_api (https://gerrit.chromium.org/gerrit/31916), and a DEPS roll(http://codereview.chromium.org/10915032/). There will be future CLs for power_manager that will use this information and test this code.
BUG=chrome-os-partner:9203
TEST=Run updated unittests.
Confirm there is no messages in the cros logs about this method being mishandled.
Review URL: https://chromiumcodereview.appspot.com/10905026
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@154905 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
Switch to Dual Display in Login screen.
BUG=145844,145158
Review URL: https://chromiumcodereview.appspot.com/10899024
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@154499 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
SessionManager,
and call them to confirm that Chromium Browser did lock/unlock the screen.
BUG=chromium-os:32457
TEST=unittests and manually verify you can lock/unlock the screen.
Review URL: https://chromiumcodereview.appspot.com/10869052
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@154273 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=chromium-os:29557
TEST=none
Review URL: https://chromiumcodereview.appspot.com/10868038
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@154244 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=115047
TBR=satorux@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10916011
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@154232 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=135245
TEST=no flags option to disable ExtendedDesktop
Review URL: https://chromiumcodereview.appspot.com/10892021
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@154035 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
StorageInfo classes.
BUG=144527
TEST=none
Review URL: https://chromiumcodereview.appspot.com/10876094
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@153825 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
MediaTransferProtocolDaemonClient::FileEntry::InitialFromResponse function.
BUG=none
TEST=none
Review URL: https://chromiumcodereview.appspot.com/10873076
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@153580 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
BUG=None
TEST=build
TBR=ben@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10878061
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@153410 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
GetSizeStatsOnFileThread is moved from disk_mount_manager.cc to file_browser_private_api.cc
BUG=None
TEST=build
TBR=estade@chromium.org, kaznacheev@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10874067
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@153402 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=none
TEST=none
Review URL: https://chromiumcodereview.appspot.com/10875012
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@152910 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Retail mode used power_manager to detect idle and active states; powerd now depends on Chrome letting it know of the user activity, which is rate limited to 5s. This introduces a delay in detecting any user activity for either the screensaver or the idle_logout dialog. Change the code to use Chrome's UserActivityDetector to detect user activity instead.
Additionally the user activity detector is also rate limited to 1s; reduce this to 200s since it is a cheap operation.
This CL also fixes a couple of other bugs that have made KioskMode unusable current builds.
1.) Get the profile for the user on the UI thread (this was being done on the file thread, causing a CalledOnValidThread check failure).
2.) Add a @ to the demo user since this is checked in gaia_auth_util.cc - CanonicalizeEmail. Not having the @ will cause a NOTREACHED.
R=derat@chromium.org
BUG=143706
TEST=The screensaver goes away as soon as the user presses a key or moves the mouse, even if it has been up for less than 5 seconds. Similarly, the idle logout dialog should cancel immidiately in case of any user activity.
Review URL: https://chromiumcodereview.appspot.com/10868004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@152895 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Make a bunch of changes to the bluetooth code to improve its testability:
- BluetoothAdapter and BluetoothDevice base observer and delegate classes
made public, allows a test to static cast the pointer and call those
methods as if it were the dbus client.
- Add MockBluetoothAdapter::Observer and MockBluetoothDevice::Observer
classes; these can be used by tests to check BluetoothAdapter and
BluetoothDevice call observer methods at the correct time, with the
correct arguments.
- Add MockBluetooth*Client::Properties classes; these mock out the
Get(), GetAll() and Set() methods so a test can verify whether or
not they're called.
Tests can also use MockBluetooth*Client::GetProperties() to return
one of these mock classes constructed statically in the test, using
ReplaceValue() on each property to set values.
BUG=none
TEST=can write a unit test
Change-Id: I9eaeb6412de891f9b1b3cdaae66d32dfecbac8c9
Review URL: https://chromiumcodereview.appspot.com/10831360
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@152234 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=139442
TEST=CQ
Review URL: https://chromiumcodereview.appspot.com/10829396
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@152168 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Remove DBus signal to power_manager::kUseNewMonitorConfigSignal since it is no
longer needed by the other side (this used to be required but it was only meant
to be temporary and the other side no longer listens for the signal).
Move DBus call to power_manager::kSetIsProjectingMethod into the DBus
PowerManagerClient class which is where the other methods in the IPC interface
live.
BUG=chromium:142039
TEST=Manually tested on Lumpy and verified that adding/removing displays results
in powerd receiving a SetIsProjecting call.
Review URL: https://chromiumcodereview.appspot.com/10831312
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@151894 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Historically, all the entry-points into the OutputConfigurator needed to refresh
their view of the cached output data. This newly-added entry-point doesn't do
this which can lead to the cached data becoming stale (since it technically only
applies within the context where the corresponding XRRScreenResources are
valid).
Ideally, no such information would be cached and every attempt to evaluate or
change the state of the video outputs would start by requesting this structure.
That change is of larger scope and risk, though, so this is the tactical
solution to the immediate problem suitable for porting to stable branches.
BUG=chromium:140807
TEST=Manually tested that ctrl-F4 and "manage displays" (in chrome://settings)
work on a Lumpy the same way with and without this change
Review URL: https://chromiumcodereview.appspot.com/10825306
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@151696 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
These stub classes are used when building Chrome on Linux with
chromeos=1. They allow sufficient UI to work to show a Bluetooth
adapter, enable and disable it, and show an unconnected fake device
associated with it.
This can be trivially extended to provide all manner of fake
Bluetooth information for UI development.
BUG=chromium-os:28555
TEST=out/Debug/chrome
Change-Id: I7af28be76355fad735389aaf2fa499d0a8dfd76b
Review URL: https://chromiumcodereview.appspot.com/10823301
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@151621 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
As a response to the suggestion made by satorux@, here is an initial OWNERS file
for chromeos/display. To begin with, I am adding myself and sque@ since other
frequent contributors should be inherited from chromeos/OWNERS.
BUG=none
TEST=none
Review URL: https://chromiumcodereview.appspot.com/10832304
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@151599 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is a patch taken over from zel's original patch:
http://codereview.chromium.org/10832258/
BUG=131915
TEST=NetworkScreenTest.* and number of other tests should start passing in BVT CrOS tests
TBR=zelidrag@chromium.org
Review URL: https://chromiumcodereview.appspot.com/10854121
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@151336 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
BUG=141825
Review URL: https://chromiumcodereview.appspot.com/10828267
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@151286 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
IPConfig interface.
BUG=chromium-os:33223,chromium:129052
TEST=built and tested with another in-process CL that will use it.
Review URL: https://chromiumcodereview.appspot.com/10824242
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@150921 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=None
TEST=ran chromeos_unittests with debug configuration
Review URL: https://chromiumcodereview.appspot.com/10831232
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@150773 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
| |
BUG=chromium-os:29557
TEST=none
Review URL: https://chromiumcodereview.appspot.com/10825170
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@150382 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=127032
TEST=ran chromeos_unittests
Review URL: https://chromiumcodereview.appspot.com/10825154
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149687 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
In IBusLookupTable::page_size actually does not affect for Chrome OS.
However, if we use chromeos-chrome on linux desktop, zero value crashes ibus's lookup table.
BUG=None
TEST=ran chromeos_unittests
Review URL: https://chromiumcodereview.appspot.com/10828114
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149580 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- IBusEngineFactoryService takes the ownership of engine_id - CreateEngine handler mapping.
- Make IBusEngineFactoryService::CreateEngine asynchronous, and introduce asynchronous unittest.
BUG=None
TEST=ran chromeos_unittests
Review URL: https://chromiumcodereview.appspot.com/10836047
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149579 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=None
TEST=ran chromeos_unittests
Review URL: https://chromiumcodereview.appspot.com/10836051
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149574 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=127493
TEST=manually checked on lumpy
Review URL: https://chromiumcodereview.appspot.com/10817028
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149382 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=None
TEST=build success
Review URL: https://chromiumcodereview.appspot.com/10827067
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149376 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently we start in mirrored mode by default every time; change this so that if the extended desktop is enabled, we default to that instead.
R=sky@chromium.org
BUG=138093
Review URL: https://chromiumcodereview.appspot.com/10836037
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149342 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=139442
TEST=CQ
Review URL: https://chromiumcodereview.appspot.com/10831059
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149304 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=126674
TEST=git try -b linux_chromeos
Review URL: https://chromiumcodereview.appspot.com/10830033
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149136 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
| |
unique and persistent across device attachments. Therefore, extract device uuid from DiskInfo::InitializeFromResponse and use that identifier while dispatching media device attached notification event.
BUG=none
TEST=none
Review URL: https://chromiumcodereview.appspot.com/10830003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149099 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
- Define member functions of class OutputConfigurator in the order
they were declared.
- Made struct CachedOutputDescription to be private member of class
OutputConfigurator. No need for it to be exposed publicly.
- Renamed "enum State" to "enum OutputState" to be more specific.
- In places where a large if block extend to the end of the function,
use an early return to reduce indentation.
BUG=chromium-os:32857
TEST=build successfully
Change-Id: Id39dff3b38d16b2496df0df288a332fe29b2e37b
Signed-off-by: Simon Que <sque@chromium.org>
Review URL: https://chromiumcodereview.appspot.com/10824071
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@149072 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
CryptohomeClient::IsMounted is converted to asynchronous and used instead.
Mock's default action for IsMounted is set in the ctor of MockCryptohomeClient.
BUG=126674
TEST=git try -b linux_chromeos
Review URL: https://chromiumcodereview.appspot.com/10817007
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@148883 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Currently when we switch between displays with extended displays turned on, the sequence is,
Mirrored -> Extended -> Extended (reversed) -> Mirrorer.
Change this to switch only between extended and mirrored displays if the extended display flag is enabled,
i.e.,
Mirrorer -> Extended -> Mirrored.
R=oshima@chromium.org
BUG=137727
TEST=Tested on a ChromeOS device with a secondary display to confirm that the inteded sequence is followed on switching displays.
Review URL: https://chromiumcodereview.appspot.com/10829026
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@148842 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
For problem description and other info please see the BUG page.
This is for DictionaryValue.
BUG=138946
TEST=N/A (no fix & no new feature)
TBR=jar scottbyer achuith agl mnissler davemoore garykac akalin hans bulach phajdan.jr jamesr
Review URL: https://chromiumcodereview.appspot.com/10834004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@148833 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This CL contains
- Make ProcessKeyEvent asynchronous and add unittest for asynchronous handling.
- Add missing signal (CommitText).
- Fix wrong signal name (UpdatePreedit -> UpdatePreeditText).
BUG=None
TEST=ran chromeos_unittests
Review URL: https://chromiumcodereview.appspot.com/10835003
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@148725 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
| |
BUG=None
TEST=ran chromeos_unittests
Review URL: https://chromiumcodereview.appspot.com/10830004
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@148537 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
| |
BUG=126947
TEST=chromeos_unittests and try bots
Review URL: https://chromiumcodereview.appspot.com/10806028
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@148068 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
With this CL, IBusEngineService can handle MethodCall and Signal emitting.
To avoid CL delta bloat, let me split the CL.
I will send CL for unit tests soon.
BUG=126947
TEST=try bots
Review URL: https://chromiumcodereview.appspot.com/10806006
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@148038 0039d316-1c4b-4281-b951-d872f2087c98
|
|
|
|
|
|
|
|
|
|
|
|
| |
Use CrypthomeClient instead.
Also make the methods asynchronous at the same time.
BUG=126674,126719
TEST=Open chrome://cryptohome
Review URL: https://chromiumcodereview.appspot.com/10703162
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@147831 0039d316-1c4b-4281-b951-d872f2087c98
|