RESOLVED INVALID67939
Missing images when -webkit-mask-box-image is applied inside -webkit-column-count
https://bugs.webkit.org/show_bug.cgi?id=67939
Summary Missing images when -webkit-mask-box-image is applied inside -webkit-column-c...
Jon
Reported 2011-09-12 09:51:54 PDT
Created attachment 107056 [details] Examples of -webkit-mask-box-image failing in a multiple column container. Screenshots and code. Overview: While -webkit-mask-box-image works as expected in typical, standalone-IMG contexts (see April 2008 post: http://www.webkit.org/blog/181/css-masks/), similarly-masked-images disappear when those IMGs exist inside a multiple-column parent (e.g., -webkit-column-count == 2, 3, etc.). See attached image for 1-col / 2-col sample screenshots of effect, plus relevant HTML and CSS. Steps to Reproduce: Apply -webkit-mask-box-image (with valid raster image) to an IMG. Assign that IMG's parent container a declaration of -webkit-column-count: 2 (and, for fullest effect, define its -webkit-column-gap as, say, 30px). Actual Results: IMG will disappear after the parent is set to multiple columns. Expected Results: IMG visible and properly cropped, while still behaving inside a multiple-column context. Build Date & Platform: Nightly (2011-09-11) build (r94932), on Mac OS 10.6.8. Additional Builds and Platforms: But does NOT appear in iOS Safari (tested on 1st-generation iPad). Appears to only affect desktop browsers (WebKit, Chrome, Safari).
Attachments
Examples of -webkit-mask-box-image failing in a multiple column container. Screenshots and code. (282.04 KB, image/png)
2011-09-12 09:51 PDT, Jon
no flags
Shane Stephens
Comment 1 2011-10-10 20:55:42 PDT
can you provide a reduced test case?
Shane Stephens
Comment 2 2011-11-23 19:22:56 PST
If you can provide actual code as a reduced test case (or failing that, at least provide the source from the attached screenshots in text form) then we can confirm this as a valid bug.
Shane Stephens
Comment 3 2012-06-27 22:03:07 PDT
Could not repro (no test case provided). Please reopen bug if you still experience this issue.
Note You need to log in before you can comment on or make changes to this bug.