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

Issue 623841 link

Starred by 4 users

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug



Sign in to add a comment

Collapsed borders don't collapse correctly across composited layer boundaries.

Reported by roie.mar...@gmail.com, Jun 28 2016

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.103 Safari/537.36

Example URL:

Steps to reproduce the problem:
Here's a minimal repro:

<body>
<table style="
    border-collapse: collapse;
">
<tbody><tr style="
    /* -webkit-filter: brightness(50%); */
">
  <td style="
    border: 5px solid red;
    background-color: green;
    /* -webkit-filter: brightness(100%); */
">aaa</td>
</tr>
</tbody></table>
</body>

Enabling the filter on the TR makes the inside of the TD's border disappear. Enabling the (no-op, I would think) filter on the TD causes the border to show fully, undarkened.

Disabling "border-collapse" on the table makes the TR's filter apply to the entire TD, including its border.

What is the expected behavior?
It's hard to say how much of the border should be counted as belonging to an individual row in collapsed borders mode, but it certainly shouldn't disappear. Also, "-webkit-filter:brightness(100%)" shouldn't have any effect on the output.

Note that this was discovered when I had 1px borders; they disappear entirely when my TR has a darkening filter.

What went wrong?
See above

Does it occur on multiple sites: N/A

Is it a problem with a plugin? N/A 

Did this work before? N/A 

Does this work in other browsers? N/A 

Chrome version: 51.0.2704.103  Channel: stable
OS Version: OS X 10.11.5
Flash Version: Shockwave Flash 22.0 r0
 
Cc: durga.behera@chromium.org
Labels: Needs-Feedback
Could you please help providing the urls with the differences and the expected output screen shots to triage further from Chrome TE side.
Status: Assigned (was: Unconfirmed)
Over to timloh@ for investigation or routing.
Owner: timloh@chromium.org
Oops, forgot the owner :)
I don't have any URLs because this is from an internal system. I can put a webpage up somewhere if you'd like (which would just be a copy of the code in my original bug report but might be more convenient for you). Let me know.

Joey

Comment 5 by timloh@chromium.org, Jun 29 2016

Components: Blink>Compositing
Labels: -Type-Compat -Needs-Feedback -OS-Mac OS-All Type-Bug
Owner: ----
Status: Untriaged (was: Assigned)
Summary: Table borders paint different with layers (was: Strange interaction between CSS filters and table borders)
http://codepen.io/anon/pen/mEWjZq

Paint/Compositing folks, could you have a look? The bug report says it's filters but it looks like it's just using any layer-inducing property (e.g. transform: translateZ(0px)).
Status: Available (was: Untriaged)
Summary: Collapsed borders don't collapse correctly across composited layer boundaries. (was: Table borders paint different with layers)
 Issue 645613  has been merged into this issue.
Project Member

Comment 8 by sheriffbot@chromium.org, Sep 11 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
Labels: -Hotlist-Recharge-Cold BugSource-User PaintTeamTriaged-20170911
Status: Available (was: Untriaged)
Project Member

Comment 10 by sheriffbot@chromium.org, Sep 12

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
Status: Available (was: Untriaged)

Sign in to add a comment