Issue metadata
Sign in to add a comment
|
Hidden DOM element is rendered
Reported by
nice...@gmail.com,
Dec 5 2017
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_1) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/62.0.3202.94 Safari/537.36 Steps to reproduce the problem: 1. Unarchive the attached html/js project(data.zip). Open feature.html?index=1 (Don't forget adding ?index=1, otherwise the page wouldn't load) You should see something like the attached screenshot(error01.jpg) 2. Locate an element with the id "page1AnimDot3" using inspector. Make sure that its visibility is hidden. 3. Check the computed style, although the element's visibility style is "hidden", its visibility is "visible"(error02.png) What is the expected behavior? The hidden style element's computed visibility should be hidden. What went wrong? The hidden element is shown. This sometimes only happens when the page cache is enabled. This bug make the hidden element visible, so ruining the overall pages. Did this work before? Yes Chrome version: 62.0.3202.94 Channel: stable OS Version: OS X 10.13.1 Flash Version: This problem happens randomly. And its not produced in Canary Version 65.0.3285.0 build.
,
Dec 5 2017
Bisect info: 498416 (good) - 498424 (bad) https://chromium.googlesource.com/chromium/src/+log/fe2758ee..da2865e8?pretty=fuller Suspecting r498417 = a87ff17992abb8eea93e035b7e355824f5ff74d9 = https://crrev.com/c/628519 by rune@opera.com "No need for forced SetStyleInternal for unchanged ComputedStyle." Landed in 62.0.3201.0 Repro note: to make bisecting easier you can add the following code inside feature.html at the very end: <script> setTimeout(function() { alert(getComputedStyle(page1AnimDot3).visibility === 'hidden' ? 'SUCCESS' : 'FAILURE'); }, 1000) </script>
,
Dec 5 2017
,
Dec 6 2017
Able to repro on Linux using Chrome stable 62.0.3202.94 but unable to repro on Linux using Chrome unstable 64.0.3278.0 Requesting reverse bisect
,
Dec 7 2017
"@Reporter: As the issue is no more seen on the latest stable 63.0.3239.84. Could you please download/install the latest chrome version stable from below link and let us know the behavior. Hence removing Needs-Bisect label. https://www.chromium.org/getting-involved/dev-channel Thanks!"
,
Dec 7 2017
As per comment#4 by bugsnash@, Providing the reverse bisect info. Able to reproduce the issue on the reported chrome version 62.0.3202.94 using Ubuntu 14.04 and Mac 10.13.1. As the issue is not seen latest canary 65.0.3285.0, hence providing reverse bisect info. Note: The issue is not seen on Windows Reverse bisect info: ----------------------------- Last Bad build : 63.0.3225.0 Revision(504540) First Good build: 63.0.3226.0 Revisio(504841) You are probably looking for a change made after 504560 (known good), but no later than 504561 (first known bad). Change Log: https://chromium.googlesource.com/chromium/src/+log/a9ba55c8571ab0d2624c83d413ccc7215a185f51..9f0c480da9cb188c82e16e6c6751875a60a114cf Review URL: https://chromium-review.googlesource.com/684186 Suspecting the same from the above change log. treib@: Please confirm the issue and help in re-assignig if it is not related to your change. Note: Assigning to treib@ as rune@ is not available in the owners list. Thanks!"
,
Dec 7 2017
,
Dec 7 2017
So if this is fixed in stable 63 as per comment 6, there's nothing to do here now, right? |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by nice...@gmail.com
, Dec 5 20177.1 MB
7.1 MB Download