etting parent element to visibility:hidden after setting child to visibility:visible hides entire element
Reported by
christia...@gmail.com,
Dec 8 2017
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.110 Safari/537.36 Edge/16.16299 Example URL: http://versatileidea.ddns.net/leimat.fi/ Steps to reproduce the problem: 1. Browse to http://versatileidea.ddns.net/leimat.fi 2. Scroll down page and see missing content after first hide/visible element 3. For comparison, browse to live version with workaround: https://www.leimat.fi What is the expected behavior? The page extensively uses hide and visible elements where first opaque:0 is set, then opaque:1. Elements should slide or fade in as text blocks enter the visible page. So essentially, element should initially be hidden, then visible. What went wrong? Refer to Issue 778873 where problem was supposed to be fixed but wasn't. https://bugs.chromium.org/p/chromium/issues/detail?id=778873 The first element works correctly. After this, all other text elements using css opaque are hidden. The develpment version of the site shows the problem. The live site has had the hidden opaque setting set to 1 as a temporary workaround Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? Yes Does this work in other browsers? Yes Chrome version: 63.0.3239.84 Channel: stable OS Version: 10.0 Flash Version: Site fails to load correctly in current Chrome and all browsers using 62/63 Chromium core (e.g. Vivaldi, Opera). Loads correctly in current versions of Firefox, Edge, IE.
,
Dec 8 2017
Debugging this page showed that the jquery.viewportchecker.js script is not working in Chrome. This most likely happened due to enabling scrollTopLeftInterop in Chrome. There is a fix in a newer version of the viewportchecker [1]. This is not at all related to issue 778873 , fwiw. [1] https://github.com/dirkgroenen/jQuery-viewport-checker/pull/55/commits/a7f37760bcf503be3171df9bf17739840c0eacf5
,
Dec 8 2017
OK, apologies for that. I confirm that the jquery.portchecker.js fix linked above did fix this issue. |
||
►
Sign in to add a comment |
||
Comment 1 by krajshree@chromium.org
, Dec 8 2017