Consider not entering docked mode if no keyboard/mouse is detected. |
||||||
Issue descriptionIf you have a laptop with a keyboard and mouse and external display connected and close the lid the device enters docked mode. This is expected and desired. What gets weird is if you have an external display but NO keyboard or mouse connected. Right now it goes into docked mode anyway. I can think of cases where that's probably what you want, but in most cases it isn't. We should really put some more thought into this case and see if we can do better. It's really jarring to close your laptop and have habit telling you that it's ok to walk away, but there's a pile of confidenial info sitting on the screen. Worse, the correction requires reopening the device and properly locking it. My initial thought is to create a policy "stay awake on lid close" and only stay awake if we detect a full set peripherals or if the policy is set.
,
Dec 20 2016
Just extra thought - I tend to close the shell of the clamshell when I connect it to an external monitor to watch movies. Even though I did not connect a keyboard and a mouse.
,
Dec 20 2016
,
Jan 8 2017
There seem to be two use cases here: 1) Allow enterprises to disable this and/or create a policy for it. Not sure if we have thought about this / enterprises asked for it? 2) For consumers. Despite the use case in c2 I may be convinced to look at least for one peripheral (e.g. a mouse) and if none are attached to not enter the mode. Also +Derat who back in the days worked on it
,
Jan 8 2017
This bug has a lot of overlap with issue 488091, if not actually being a duplicate of it. That bug is long and unusable, though, so I understand starting a new one. :-P I'm not sure that powerd (which makes the call about entering docked mode based on lid-switch events and Chrome telling it that there's an external display) currently has any knowledge about whether there are external input devices. Probably that could be added, though. We'd need to handle both Bluetooth and USB devices. #2: Yes, that use case would be broken by this. A less-convenient workaround would be turning the backlight brightness down, but it would no longer be possible to just close the lid when displaying a movie on an external display. (The behavior when casting is a bit more complicated; see the other lengthy bug.) We could at least avoid affecting the majority of users, who don't have "Require password to wake from sleep enabled", if we enter dock mode as usual but lock the screen if that pref is set and there are no input devices connected. I'm pretty much restating the conversation from issue 488091 now, though.
,
Jan 9 2017
It sounds to me that what we need is to "lock" the screen, but not "not entering docked mode", and makes sure that if it will suspend after no activities (basically behave like non docked mode from power/lock point of view)? If so, a possible stop gap solution is to lock the screen upon entering docked mode.
,
Aug 30 2017
,
Aug 30 2017
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by abodenha@chromium.org
, Dec 15 2016