Issue metadata
Sign in to add a comment
|
Fixed Div-Element in Frameset disappears on scroll
Reported by
sonnyp...@gmail.com,
Apr 18 2018
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:59.0) Gecko/20100101 Firefox/59.0 Steps to reproduce the problem: 1. Open frameset.html in Chrome, there is a red div-element 2. Scroll down (my resolution 1920px x 1080px) 3. red div-element disappears What is the expected behavior? red div-element should not disappear What went wrong? Fixed Div-Element in Frameset disappears on scroll Did this work before? Yes 65.* Does this work in other browsers? Yes Chrome version: 66.0.3359.117 Channel: n/a OS Version: 10.0 Flash Version: It works in every other browser except chrome 66.*
,
Apr 18 2018
,
Apr 19 2018
Unable to reproduce this issue on reported version 66.0.3359.117 using Windows 10 . Attaching screencast for reference. Steps: 1. Openend frameset.html in Chrome, there is a div-element 2. Scrolled down and observed (my resolution 1920px x 1080px) 3. red div-element doesnot disappears 4. Also verified Index.html & Html. @Reporter: Please check the video and let us know if we miss anything. Could you also check by resetting all flags to default. Any further information on reproducing the issue would help in better investigation. Thanks!
,
Apr 23 2018
Thank you for your reply! Did you really just opened frameset.html and scrolled down to bottom? index.html must be there. Tried it on 4 different computers (all windows 10), was able to reproduce it at all by just downloading the two files and opening frameset.html (dont edit files).
,
Apr 23 2018
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Apr 24 2018
Able to reproduce the issue on reported version 66.0.3359.117 & tested on latest canary 68.0.3404.0 using Ubuntu 14.04, Windows 10 and Mac OS 10.13. hence providing bisect information below. Bisect Info: ================ Good build: 66.0.3347.0 Bad build: 66.0.3348.0 You are probably looking for a change made after 536891 (known good), but no later than 536892 (first known bad). CHANGELOG URL: https://chromium.googlesource.com/chromium/src/+log/296e89cb3e93e39b3caa810bc3df1d67e5de4e0e..39cb84e649e045d2233a395009d5ccf1d08854a0 suspect: https://chromium.googlesource.com/chromium/src/+/39cb84e649e045d2233a395009d5ccf1d08854a0 Reviewed-on: https://chromium-review.googlesource.com/919644 @David: Please confirm the issue and help in re-assigning if it is not related to your change. Thanks!
,
Apr 24 2018
,
Apr 24 2018
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by sonnyp...@gmail.com
, Apr 18 2018Additionally you ca reproduce it in an iframe. <!DOCTYPE html> <html> <head> <title>Test</title> </head> <body> <iframe src="index.html"></iframe> </body> </html>