New issue
Advanced search Search tips

Issue 837191 link

Starred by 3 users

Issue metadata

Status: WontFix
Owner:
Closed: Apr 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac
Pri: 2
Type: Bug



Sign in to add a comment

chrome new version 66, not getting box shadow,border for division.

Reported by rijinram...@gmail.com, Apr 26 2018

Issue description

Chrome Version       : 66.0.3359.117
OS Version: 10.0
URLs (if applicable) :
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari:OK
    Firefox:OK
    IE/Edge:OK

What steps will reproduce the problem?
1.I create a i frame.
2.set style border,box-shadow.


What is the expected result?
 border and box-shadow display.

What happens instead of that?
 border and box-shadow not displaying in chrome 66 version. but getting the expected result in chrome 65, firefox,safari.


Please provide any additional information below. Attach a screenshot if
possible.

UserAgentString: Mozilla/5.0 (Windows NT 10.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.117 Safari/537.36



 
chrome.PNG
88.8 KB View Download
firefox.PNG
183 KB View Download

Comment 1 by woxxom@gmail.com, Apr 26 2018

There must be something else in your case because the following html works in Chrome 66:
<iframe style="
    position: fixed;
    bottom: 10%;
    right: 10%;
    background: white;
    border: 2px solid #62afff;
    border-radius: 10px;
    box-shadow: 11px 17px 30px #005aca88;
"></iframe>

Comment 2 by woxxom@gmail.com, Apr 26 2018

Apparently it's https://www.articbot.com and the iframe is shown after clicking the blue thingamajig in the bottom right corner, but the shadow is displayed here in Chrome 66. See if you can reproduce the bug in a new profile without any extensions. See if disabling hardware acceleration in browser settings helps. In case it does, attach the contents of chrome://gpu page.

Comment 3 Deleted

Comment 4 Deleted

.articbot001chat {
    all: unset;
    position: fixed;
    bottom: 100px;
    right: 30px;
    background-color: #33b8cc;
    background-image: none;
    border-radius: 10px 10px 10px 10px;
    padding: 0 0 0 0;
    margin: 0 0 0 0;
    box-sizing: border-box;
    border: none;
    float: none;
    box-shadow: 0 0 10px grey;
    overflow: hidden;
}

when i am removing the border-radius, box shadow working fine. this is the issue i am facing. but in the previous chrome version it works fine.
chrome_66.PNG
124 KB View Download
Components: Blink>Paint
Labels: -Pri-3 Needs-Feedback OS-Android OS-Chrome OS-Linux OS-Mac Pri-2
NextAction: 2018-05-14
Status: Available (was: Unconfirmed)
The clip for the iframe border radius is clipping out the shadow. I see it in 66.0.3359.117

woxxom@, what version are you seeing the shadow on? We fixed a regression at some point related to iframe overflow clipping and I suspect that fix is causing this issue.

A reduced test case would be excellent. Is it just any non-composited iframe with border radius and a shadow?

Comment 8 by woxxom@gmail.com, Apr 26 2018

Sorry for misleading, my Chrome 66 had chrome://flags/#enable-experimental-web-platform-features enabled, which prevented the bug.

Comment 9 by woxxom@gmail.com, Apr 26 2018

A reduced test case is attached, it's basically #c1 with a yellow background.
test.html
224 bytes View Download
Labels: -Needs-Feedback
NextAction: ----
Thanks woxxom@, that's super helpful.

It's odd to me that experimental-web-platform-features makes any difference. Maybe it's fixed by OOPIF.
Owner: schenney@chromium.org
Status: Assigned (was: Available)
Cc: chrishtr@chromium.org wangxianzhu@chromium.org
As expected, bisects to https://chromium.googlesource.com/chromium/src/+/d03257dd6231949a244fea41890a35b7707f5f08 which was the patch re-adding overflow clip for non-composited iframes. However, it requires --disable-blink-features=SlimmingPaintV175 to reproduce.

My sense is that we should WontFix this because SPv175 is rolling out in M-67 so the bug will disappear shortly. Other thoughts on prioritizing this?
Agreed, WontFix if it is only if SPv175 is off. Please triple check that
that is the case though..
Status: WontFix (was: Assigned)
Every bisect run I tried without disabling SPv175 resulted in correct rendering, so I'm confident SPv175 fixes the issue. And I tried a lot of bisect runs because  I knew that this probably worked then didn't then did then didn't, and I was trying to isolate each state.
Cc: vamshi.kommuri@chromium.org
 Issue 843915  has been merged into this issue.
Cc: susan.boorgula@chromium.org
 Issue 847181  has been merged into this issue.

Sign in to add a comment