New issue
Advanced search Search tips

Issue 879693 link

Starred by 15 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug



Sign in to add a comment

Video control wrong stacking order

Project Member Reported by weiliangc@chromium.org, Aug 31

Issue description

Repro-ed on both linux and CrOS M68.

Open a crbug with video content, such as crbug.com/875020, scroll until video control is near top of page.

The header of crbug.com will occlude the video, but the play button as well as the progress bar at bottom will show up on top of the header.

Also tried turning on Video on SurfaceLayer but issue remains.

If I turn on layer borders, looks like the video control is on another layer on top of the video.
 
Screenshot 2018-08-31 at 3.45.49 PM.png
123 KB View Download
Screenshot 2018-08-31 at 3.46.21 PM.png
410 KB View Download
Screenshot 2018-08-31 at 3.52.33 PM.png
465 KB View Download
Owner: chrishtr@chromium.org
Status: Assigned (was: Untriaged)
The reason is that the video is not a positioned element, but both the position:sticky header and the controls are positioned, and the controls
are later in paint ordre than the position:sticky element.

Within a given stacking context, the spec says to paint non-positioned elements first,
then positioned elements.

This is why the video paints before the position:sticky paints before the control.

This could be worked around by avoiding positioning in the video controls, but that
could have negative effects on compositing, due to limitations of the SPv1 compositing
algorithm.

I think the right long-term solution is to make video elements an "replaced normal-mode
stacking context" (see paint_layer.cc), similar to what was done for <foreignObject>.
But this change unfortunately relies on SPv2.
Labels: -Pri-2 Pri-3
 Issue 915726  has been merged into this issue.
Cc: beccahughes@chromium.org dalecur...@chromium.org steimel@chromium.org swarnasree.mukkala@chromium.org w...@chromium.org susan.boorgula@chromium.org
 Issue 848405  has been merged into this issue.
Issue 920670 has been merged into this issue.

Sign in to add a comment