New issue
Advanced search Search tips

Issue 885161 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 880825
Owner: ----
Closed: Sep 20
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 3
Type: Bug



Sign in to add a comment

text with -webkit-text-fill-color: transparent not appearing

Reported by jroter...@gmail.com, Sep 18

Issue description

Chrome Version       : 69.0.3497.100
URLs (if applicable) :https://www.allwaysforward.org/fillthehill/
Other browsers tested:
  Add OK or FAIL after other browsers where you have tested this issue:
     Safari: PASS/FAIL (Version)
    Firefox: PASS/FAIL 62.0 OK
       Edge: PASS/FAIL  42.17134.1.0 OK
     Chrome: PASS/FAIL 68.0.3440.106 OK

What steps will reproduce the problem?
(1) load the URL https://www.allwaysforward.org/fillthehill/
(2) inspect the first H1 tag. If there is a fallback style for -webkit-text-fill-color, disable it so that the 'transparent' rule is in effect.

What is the expected result?
The H1 heading should display as transparent text revealing a pink patterned background image. 


What happens instead?
No H1 heading text appears (unless you reveal it by highlighting the text).


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


For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

 
2018-09-18_9-11-33.png
93.7 KB View Download
Labels: Needs-Triage-M69
Cc: susan.boorgula@chromium.org
Components: Blink>CSS
Labels: Triaged-ET
Mergedinto: 880825
Status: Duplicate (was: Unconfirmed)
jrotering@ Thanks for the issue.

This issue looks similar to  issue 880825 . Hence merging this issue to  issue 880825 .
Please feel free to undupe if it is not similar.

Thanks..
I don't think this is an issue of 880825 because it doesn't use display:table.  

After posting the issue I did realize that it is somehow related to the presence of an :after style on the h1. If you remove the :after pseudo-element the -webkit-background-clip: text does work properly. So it has something to do with the interplay between the background-clip and the :after element being present.

Sign in to add a comment