New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 780679 link

Starred by 2 users

Issue metadata

Status: Fixed
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Wayland client apps in immersive mode, the header cannot be revealed

Project Member Reported by wutao@chromium.org, Nov 2 2017

Issue description

ToT as of 8001500f052d3a126e874e3ef154e80fd3c5bd7b

1. Launcher ChromeOS with --enable-wayland-server
2. Run wayland client, e.g. wayland_rects_client
3. Press F4 to put wayland app into immersive mode
4. Use mouse to reveal the header

The header is not revealed.

 
Where is immersive mode revealing of the header implemented for chrome apps?

Exo uses ash::CustomFrameViewAsh for windows with a frame (not Arc++ windows).
It actually works, but with two issues:
1) wayland_rects_client does not fill the screen in immersive fullscreen and
   you have to move the cursor to the top within the region that application draws. I haven't looked into details, but I believe geometry isn't set to fill the screen?
2) the header is behind the application window because the widget is behind the surface host.

I actually knew 2) and was going to work on it as a part of ARC++ frame on chrome.

I'm not sure what is expected behavior of the app in 1) scenario, but I'll have to deal with similar situation for ARC++ (wide caption).
Components: UI>Shell>Immersive

Comment 4 by osh...@chromium.org, Mar 23 2018

2) is fixed now. just fyi.
Owner: osh...@chromium.org
Status: Assigned (was: Untriaged)
oshima@ who do we assign 1) to?

Comment 6 by osh...@chromium.org, Apr 17 2018

Status: Fixed (was: Assigned)
It'll be handled in crbug.com/832496. Let me close this because you can reveal it now at least.

Sign in to add a comment