Issue metadata
Sign in to add a comment
|
scrollIntoView not working in grids
Reported by
mamek...@googlemail.com,
Oct 3
|
||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.1; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.100 Safari/537.36 Steps to reproduce the problem: 1. create a display grid div composition 2. fill any of containing divs with any html code 3. use scrollIntoView in one of the divs What is the expected behavior? the grid layout should be placed as before What went wrong? the complete grid layout will be completely destroyed and scoll up. Did this work before? Yes 68 Chrome version: 69.0.3497.100 Channel: stable OS Version: 6.1 (Windows 7, Windows Server 2008 R2) Flash Version: F***!
,
Oct 3
The problem exists only on scrollIntoViewOptions with block "start", "end" will working. I see no workaround, it always results in a complete layout desaster. My grid has position "relative", position "absolute" will also not working. All elements above the grid are not scrollable. In the example images the grid is the area from the menu line to the footer (all palette windows). And: After the call the deskop is visible in the browser page window (two lines at the bottom). :-o
,
Oct 4
mamekudz@Thanks for filing the issue... @Reporter : As per comment #0 tried to create a file and also observed the page " https://www.w3schools.com/jsref/met_element_scrollintoview.asp " but we are not sure. It would be really helpful if a sample URL/Test file is provided, so that we can investigate the issue further. Thanks.!
,
Oct 4
,
Oct 5
Thank you for your answer. My web application is very complex and currently only running on my developement system, but I have save an offline file of the generated page you can download: http://www.oxyd.games/OxydIntoViewTest.zip After unzipping, you can load it offline (be sure that dev console is offline to prevent debugging while loading), then open dev console and enter: document.getElementById("lshcf_0_10").scrollIntoView(true); <= this will show you the bug. document.getElementById("lshcf_0_10").scrollIntoView(false); <= this works In my orignial code I use .scrollIntoView({block:"start",behavior:"smooth"}); <= not working .scrollIntoView({block:"end",behavior:"smooth"}); <= my current workaround
,
Oct 5
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
,
Oct 8
mamekudz@ Thanks for the feedback...
As per comment #5, Tried to reproduce the issue on reported chrome 69.0.3497.100 Using windows 7. Attaching screencast for reference.
Steps:
1. Launched reported chrome
2. Downloaded given file and extracted zip file
3. Dragged file and opened opened in new tab and then opened Dev tools > Console > Entered
>1. document.getElementById("lshcf_0_10").scrollIntoView(true);
>2. document.getElementById("lshcf_0_10").scrollIntoView(false);
for both seen same behavior.
4. Restarted chrome Navigated > Network > Checked Offline > Dragged the file and opened in new tab > Observed the error as per screencast.
@Reporter: Could you please check the attached screen cast and please let us know if anything missed from our end and observed the same behavior from M-60 and to latest chrome M-71.
Thanks..!
,
Oct 8
Why there is only a black screen in your screencast?
,
Oct 8
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
,
Oct 8
...perhaps you have to disable javascript debugger in developer console settings before loading the file. This offline file is only a snapshot of a web application which not included all javascript files, so the resulting javascript errors will prevent building the dom. The included dom is needed to show you the bug.
,
Oct 9
mamekudz@ Thanks for the feedback... As per comment #10 and comment #5, Tried to reproduce the issue on reported chrome 69.0.3497.100 using Windows 10 and 7. Attaching screencast for reference. Steps: ----- 1. Launched chrome 2. Opened Dev tools > Setting > Checked the Disable JavaScript 3. Opened File in new tab As we are observed same behavior as per comment #7 and also followed the comment# 7 steps too. @Repoter: Could you please check the attached screen cast and please let us know if anything missed from our end. If possible provide screencast for better triaging it. Thanks...!
,
Oct 9
Ok, I think I have found the problem: Your unzipper does not handle some characters in the correct way. In your screencast the files and folders are wrong named, it have to be named "Oxyd®" and "Oxxd®_files". Please download the zip file again, I have removed all the problematic characters from the filenames and file contents. And: In your screencast I can see that javascript debugging is NOT disabled. There are already debugging messages in your console: "Uncaught ReferenceError. Menu is not defined". The best way is to open a new tab, open dev console, switch off js debugging and then load the offline file to the open tab. Thank you for your patience.
,
Oct 9
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
,
Oct 10
mamekudz@ Thanks for the feedback... As per comment #12, Tried to reproduce the issue on reported chrome 69.0.3497.100 using Windows 7 and 10. Still we are getting blank screen and errors on Dev tools (same as comment #11 and comment #7). Hence requesting Blink>Scroll team look into it and adding TE-NeedsTriageHelp label to it. Thanks..!
,
Oct 10
,
Oct 26
mamekudz@: I can't reproduce the issue based on your link above, either with or without Javascript disabled. The page looks correct to me (at least not scrolled off screen) Can you provide a reduced test case that reproduces the issue?
,
Oct 26
,
Nov 1
Pinng, mamekudz@ - can you please provide a reduced test case or help me reproduce on the link you gave. If we cannot reproduce the issue this isn't actionable and we'll have to close the bug unfortunately.
,
Nov 5
I just test it at version 70.0.3538.77, the bug is still present. I used the link. I don't understand what is going wrong so you can't reproduce the bug. But I noticed that sometimes scrollIntoView have absolute no effect in this test case. Ok, it is not easy, but I will look for a reduce test, but it will take some time.
,
Nov 5
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
,
Nov 5
,
Nov 9
The NextAction date has arrived: 2018-11-09
,
Nov 9
,
Nov 14
mamekudz@ A Gentle ping.. As per comment #19, request you to provide a reduced test where this issue can be reproduced, which will help in further triaging. Thanks,..
,
Nov 23
The NextAction date has arrived: 2018-11-23
,
Nov 25
Hi, I am sorry, but I did not succeed to create a simple test which reproduce the problem. Anyway there is a bug in "ScrollIntoView", also if I set a property "position:fixed" to the grid, it will change the position. I will have a look at this bug in the future and if I find any conditions which will trigger this bug then I will reopen this ticket. Thanks and regards Meinolf
,
Nov 25
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
,
Nov 29
@Reporter: As per comment #26, adding Needs-Feedback label to it and if possible provide a sample test file/url, so that we can investigate the issue further. Thanks.!
,
Dec 6
Closing this for now. Reporter feel free to reopen this bug or file a new one when you got the information requested. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by phanindra.mandapaka@chromium.org
, Oct 3