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

Issue 758351 link

Starred by 1 user
Status: Available
Owner: ----
Cc:
█ trchen@chromium.org
pdr@chromium.org
chaopeng@chromium.org
bokan@chromium.org
vmp...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 3
Type: Feature



Sign in to add a comment

Paint scrollbars after the border to match firefox

Project Member Reported by pdr@chromium.org, Aug 23 2017 
Edge, Firefox, and Blink all differ in the paint order of negative z-index children, borders, and scrollbars: https://output.jsbin.com/vikiyam/quiet.

I think we should change our paint and hit test order to match firefox so that scrollbars are painted immediately after borders in the paint algorithm: https://www.w3.org/TR/CSS2/zindex.html.

Comment 1 by pdr@chromium.org, Aug 23 2017

Cc: bokan@chromium.org trchen@chromium.org
Tien-ren made a good point that overlay scrollbars are necessarily different because they need to paint on top of positive z index in-flow children like the green box in this example: http://output.jsbin.com/cuquvuv/quiet

Comment 2 by chrishtr@chromium.org, Aug 24 2017 

Does anyone know of a spec that says when scrollbars should be painted?
If not we should also file a spec bug.

Does Firefox change its paint order for overlay scrollbars? It seems so.

Comment 3 by schenney@chromium.org, Aug 24 2017

Labels: BugSource-Team PaintTeamTriaged-20170823 OS-Android OS-Chrome OS-Linux OS-Mac OS-Windows

Comment 4 by chaopeng@chromium.org, Aug 24 2017

Cc: chaopeng@chromium.org
Project Member

Comment 5 by sheriffbot@chromium.org, Aug 27

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

Comment 6 by schenney@chromium.org, Aug 27

Status: Available (was: Untriaged)
►

Sign in to add a comment