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

Issue 709460 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 709533
Owner:
Closed: Apr 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Border-radius causes sibling element to be hidden

Reported by jopperhe...@gmail.com, Apr 7 2017

Issue description

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

Example URL:
https://jsfiddle.net/no2zmktz/3/

Steps to reproduce the problem:
1. Visit the provided url: https://jsfiddle.net/no2zmktz/3/
2. Check or uncheck the checkbox apply border-radius to the title and see the text appearing/disappearing.

Happens in:
Chromium 59.0.3066.0 (Developer Build) (64-bit)
Chrome  57.0.2987.133 (64-bit)

What is the expected behavior?
The text should always be visible. This is the case in Firefox 52.0.2 (64-bit), Chrome 56 and Safari (10.0.3 (12602.4.8) ).  

What went wrong?
The border-radius property on one element makes its sibling invisible. This happens with backface-visibility: hidden set on the parent container and overflow:hidden is applied.  

Does it occur on multiple sites: N/A

Is it a problem with a plugin? No 

Did this work before? Yes Chrome 56

Does this work in other browsers? Yes

Chrome version: 57.0.2987.133  Channel: stable
OS Version: OS X 10.12.3
Flash Version:
 

Comment 1 by a...@chromium.org, Apr 7 2017

Components: Blink>Layout
Labels: Needs-Bisect
Status: Untriaged (was: Unconfirmed)
This needs attention by Blink folks. Could probably stand to have a bisect too.

Comment 2 by e...@chromium.org, Apr 8 2017

Components: -Blink>Layout Blink>Compositing
Looks like an issue with backface-visibility, tentatively over to the compositing team.

Comment 3 by ajha@chromium.org, Apr 10 2017

Labels: Needs-Triage-M57
Cc: ranjitkan@chromium.org
Labels: -Pri-2 -Type-Compat -Needs-Bisect -Needs-Triage-M57 hasbisect-per-revision ReleaseBlock-Stable M-58 OS-Android OS-Chrome OS-Linux OS-Windows Pri-1 Type-Bug-Regression
Owner: schenney@chromium.org
Status: Assigned (was: Untriaged)
Able to reproduce the issue and is broken in M57. Below is the bisect details obtained from per revision Bisect:

57.0.2948.0 - Good Build
57.0.2950.0 - Bad Build

Change Log:
https://chromium.googlesource.com/chromium/src/+log/8c0be82a912cb5ef954980c924c32b99740f761c..0cfffd46dfaa1ee93d3d667f82b2fb3721078b34

@schenney: Assigning to you, request you to please take a look into it. Please help us to find an owner if not with respect to your change.

Tagging to M58 milestone and stable blocker. Please undo or change if not the case.

Thanks.!
In your application, do you really need backface-visibility: hidden?

That causes creation of composited content for the spans, revealing the bug.

I'm trying to assess the priority on this, and knowing how it is affecting you will help us do that.
The backface-visibility property is in a css file on which many individual projects are based. Since the majority of the css used in those projects is pretty simple, the property is not needed in most of our cases. Unfortunately it's a huge amount of work to be completely sure, because I'd have to check everything manually.

Thanks for looking into it, I really appreciate it.
Labels: -M-58 M-59
I appreciate that removing something in a very common CSS file is risky. However, it might be having a significant detrimental performance impact on your page, so worth experimenting with.
Mergedinto: 709533
Status: Duplicate (was: Assigned)

Sign in to add a comment