New issue
Advanced search Search tips

Issue 762966 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Mac
Pri: 2
Type: Bug



Sign in to add a comment

SVG mix-blend-mode via CSS only working when DOM element is present

Reported by benjamin...@cyanjoe.com, Sep 7 2017

Issue description

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

Steps to reproduce the problem:
1. Create an inline SVG, including 2 overlapping layers
2. Add a class to the top layer that includes a mix-blend-mode property
3. The top layer renders as it wouldn't have a mix-blend-mode property

What is the expected behavior?
In the attached test file a line should be rendered that is partially gray. Also a gray box should be rendered.

What went wrong?
The path is indeed partially gray but the gray box was not rendered. Instead the background is just white.

Did this work before? No 

Does this work in other browsers? No
 Tested on the following Browsers:
- Firefox: OK
- Chrome (61, 63, Chromium): FAIL - workaround works
- Opera: FAIL - workaround works
- Edge: FAIL
- MSIE 11: FAIL

Chrome version: 61.0.3163.79  Channel: stable
OS Version: OS X 10.12.6
Flash Version: 

There is a simple workaround (which also works in Opera):
Adding a non-SVG element with any mix-blend-mode will trigger a correct mix-blend-mode rendering inside the SVG.
 
svg-mix-blend-mode.tar.gz
2.0 KB Download

Comment 1 by f...@opera.com, Sep 7 2017

Labels: OS-Linux
Status: Available (was: Unconfirmed)
I take it adding style="isolation: isolate" to the <svg> element would also workaround this issue? Probably a dupe, to some degree, of  issue 738810 .
Yes, probably this issue relates to  issue 738810 .
Added `isolation: isolate` to the <svg> and indeed it renders correctly.
Project Member

Comment 3 by sheriffbot@chromium.org, Sep 7

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)
Still broken despite 738810 being marked as WontFix. I guess this is a worse case of the same issue.

Sign in to add a comment