Issue metadata
Sign in to add a comment
|
opacity: 1 turn objects invisible
Reported by
david.pr...@gmail.com,
Jun 26 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.40 Safari/537.36 Example URL: https://jsfiddle.net/david_proweb/1md5uezx/ Steps to reproduce the problem: Open this page: https://jsfiddle.net/david_proweb/1md5uezx/ I could not reduce more than that (but is possible). What is the expected behavior? This is a slider plugin that I have developed. Maybe about two or four months ago it worked. It basically do a fade effect from a image to another, animating the first image to opacity 0% and the next image to 100% (and so on, in a looping). What went wrong? For some reason, when style:opacity reach to 1 (100%) it make the image content invisible. When I modify the script to 0.9999 (99.99%) it works (line 74). But now the most strange thing: if I modify the CSS content just appending a useless comment in a specific place, it works. On CSS side, put a comment after `float: left` on line 8. Before: (not working) https://jsfiddle.net/david_proweb/1md5uezx/ .sliderWidget > .wrapper > .content > .elements > .element { display: inline-block; float: left; overflow: hidden; } After: (working) https://jsfiddle.net/david_proweb/1md5uezx/1/ .sliderWidget > .wrapper > .content > .elements > .element { display: inline-block; float: left; // Just a comment, serious. overflow: hidden; } Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? Yes 4 month ago (more or less) Does this work in other browsers? Yes Chrome version: 60.0.3112.40 Channel: beta OS Version: 10.0 Flash Version:
,
Jun 26 2017
,
Jun 26 2017
,
Jun 27 2017
,
Jun 28 2017
Able to reproduce the issue on Windows 10, Ubuntu 14.04 and Mac 10.12.5 using reported version #60.0.3112.40 and latest canary #61.0.3142.3. Bisect Information: ===================== Good build: 60.0.3097.0 Revision(471158) Bad Build : 60.0.3098.0 Revision(471507) Change Log URL: https://chromium.googlesource.com/chromium/src/+log/9d3cbf5bb0cca7fdcbfa22c63a18008e242f3bc9..d31013d806afc0c5dce0c24e40c30f97a4adf972 From the above change log suspecting below change Review URL: https://codereview.chromium.org/2875163002 glebl@ - Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner. Note: 1. Adding label ReleaseBlock-Beta as it seems to be a recent regression. 2. Unable to run new bisect script as chrome doesn't invoke for the above revision range. Thanks...!!
,
Jun 28 2017
,
Jun 28 2017
,
Jun 28 2017
,
Jun 28 2017
The issue is probably the HasSelfPaintingLayer query in the offending patch, which changes when opacity goes to 1 because that changes the stacking context. That is, the bisect is very plausible.
,
Jun 28 2017
Gleb is no longer on the team. Over to robhogan to see if this can be fixed easily or if we should revert his patch.
,
Jun 29 2017
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by david.pr...@gmail.com
, Jun 26 201749.6 KB
49.6 KB View Download