New issue
Advanced search Search tips

Issue 661020 link

Starred by 4 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 3
Type: Bug

Blocking:
issue 874753



Sign in to add a comment

translateZ(0) causes incorrect painting on fieldset legend

Reported by evan.tri...@gmail.com, Nov 1 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/53.0.2785.143 Safari/537.36

Steps to reproduce the problem:
1. Run the attached html file

What is the expected behavior?
There is no black strip at the top of the fieldset.

What went wrong?
There is a black strip at the top of the fieldset. See attached file.

Did this work before? N/A 

Does this work in other browsers? Yes

Chrome version: 53.0.2785.143  Channel: n/a
OS Version: 10.0
Flash Version: Shockwave Flash 23.0 r0

If you toggle translateZ(0) in the inspector it causes the issue to go away.

This issue appears to be resolved in Chrome 54 and the Canary builds, however I wanted to bring the issue to your attention so a test case can be added if necessary because this sounds like it may have been resolved inadvertently.
 
raw.html
429 bytes View Download
fieldset_bug.png
1008 bytes View Download
Components: Blink>Paint
Status: WontFix (was: Unconfirmed)
The problem was probably with clearing composited layers, and you managed to find a case that broke it. We appreciate you reporting and the test case. Our approach is to close this out as already fixed, which means it will live on as historical reference.

Labels: M-56 Needs-Bisect OS-Linux
Status: Available (was: WontFix)
I can reproduce on 56.0.2902.0 / Linux.
Testers, please bisect on Linux and also on Windows to see where it was fixed
for the latter but not the former.
NextAction: 2016-11-04
Status: Untriaged (was: Available)
Cc: chrishtr@chromium.org
Labels: -Needs-Bisect
Able to reproduce the issue on Windows 10 and Ubuntu 14.04 using 53.0.2785.143,latest stable 54.0.2840.87/90,Beta 55.0.2883.28 and canary 56.0.2906.0.
This is a non-regression issue since 41.0.2215.0.
Note : This is working fine on Mac 10.11.6 using 53.0.2785.143,latest stable 54.0.2840.87,Beta 55.0.2883.28 and canary 56.0.2906.0.

chrishtr@ : Could you please take a look into this if you need further info on it.
Labels: -Pri-2 Pri-3
NextAction: ----
Status: Available (was: Untriaged)
The test requires overflow: hidden and margin: 0 0 10px on the fieldset.
The black background is not because of under-painting I think, because if I
put a background color on the parent div it does not show. There is just black
painted. Probably because paint order is messed up? when painting the fieldset
when composited? Not sure.
Components: -Blink>Paint Blink>Compositing
It's not failing on trunk for me. Is there an updated test case that does?

One possibility is that the gap in the border is causing painting of the border to go wrong, but there's no reason to expect composited/not to influence that.
The testcase in the original bug filing fails for me on Linux ToT.
Project Member

Comment 11 by sheriffbot@chromium.org, Nov 6 2017

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. If you change it back, also remove the "Hotlist-Recharge-Cold" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Components: -Blink>Compositing Blink>Paint
Labels: -Hotlist-Recharge-Cold
Status: Available (was: Untriaged)
Attached is a slightly modified test case that more readily shows the problem.

The composited div containing the fieldset and its legend does not repaint its background when you disable the parent (body) background. There are a couple of possibilities. We might be invalidating incorrectly or  the clip for overflow might be applied at the div instead of the fieldset (evidence that you need overflow set to reproduce the problem suggests that's so) or the repaint area might be wrong.
raw.html
460 bytes View Download
Blocking: 874753

Sign in to add a comment