New issue
Advanced search Search tips

Issue 637907 link

Starred by 2 users
Status: Untriaged
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Dock mode + frecon displays on internal display; doesn't re-blank

Project Member Reported by dnschn...@chromium.org, Aug 15 2016 
Google Chrome	53.0.2785.55 (Official Build) beta (64-bit)
Platform	8530.49.0 (Official Build) beta-channel samus
ARC	3127873

What steps will reproduce the problem?
(1) Attach an external display
(2) Set the brightness to 0 to enable dock mode; leave lid open
(3) Switch to frecon (Ctrl+Alt+Forward)
(4) ISSUE A: panel lights and frecon appears on the internal display, not the external one
(5) Switch back to Chromium OS (Ctrl+Alt+Back)
(6) ISSUE B: panel stays lit and the login prompt for frecon is still visible, although panel is not part of the active workspace (i.e., Chromium OS is still in dock mode)

What is the expected output?
frecon should ideally appear on one of the external displays.
If frecon has to appear on the internal display, the internal display should at least turn off again when switching back, and its contents should be cleared (instead of displaying the stale frecon image).

Comment 1 by dnschn...@chromium.org, Aug 15 2016

Summary: Dock mode + frecon displays on internal display; doesn't re-blank (was: Dock mode + frecon displays on internal display; doesn't re-mute)

Comment 2 by vsu...@chromium.org, Aug 16 2016

Components: UI>Shell>Kiosk

Comment 3 by vsu...@chromium.org, Aug 16 2016

Components: -UI>Shell>Kiosk

Comment 4 by keta...@chromium.org, Feb 17 2017

Status: Archived (was: Untriaged)

Comment 5 by ketakid@google.com, Mar 18 2017

Status: Available (was: Archived)
Activating. Please assign to the right owner and the appropriate priority.
Project Member

Comment 6 by sheriffbot@chromium.org, Apr 12 2018

Labels: Hotlist-Recharge-Cold
Status: Untriaged (was: Available)
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue.

Sorry for the inconvenience if the bug really should have been left as Available.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
►

Sign in to add a comment