Issue metadata
Sign in to add a comment
|
Scroll related issue in chrome browser
Reported by
zebracom...@gmail.com,
Dec 17
|
||||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: 1. Open google chrome browser : 71.0.3578.98 2. Open image related HTML in google chrome browser 3. scroll top to bottom. What is the expected behavior? Page should not scroll more then image. What went wrong? page is scrolling more than image. Did this work before? Yes 50.0.2661.89 Chrome version: 71.0.3578.80 Channel: n/a OS Version: 8.1 Flash Version: 71.0.3578.98 It is working fine in Google chrome 50.0.2661.89. Is there any setting or configuration change which will make it working.
,
Dec 18
,
Dec 18
@zebracompany1: We do not have access to link provided in c#1. Could you please attach video here or upload in drive and share it here. Along with it please provide URL on which this issue is seen along with device details. Thanks!
,
Dec 19
Please find the below link of the video uploaded in drive, https://drive.google.com/open?id=18kBD8yzWxp55flp1XyeeUWlDe-m5M0Bb Issue is seen in Android Oreo device, and we had created a URL on the local server.
,
Dec 19
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
,
Dec 21
@ zebracompany1: Does this happen when you open html file directly in browser or seen only when opening through server? Could you please provide test file to test this issue. We tested with attached HTML file. Steps used: ========== 1. Downloaded attached HTML file, opened Files app, Opened HTML page 2. Selected 3 dot menu and opened with chrome stable, dev and canary. 3. On scrolling from left to right or top to bottom or vice versa image doesn't scroll as shown in video of c#4. Please provide test URL to test this issue from our end. Thanks!
,
Dec 21
,
Dec 21
,
Dec 24
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
,
Dec 27
Hi, would like to know if there is any update on this issue?
,
Dec 27
I'm not sure what the expectation is but the behavior in the video for M71 appears correct to me. If you can zoom in, you should be able to scroll around. If the in tent is that page shouldn't not be scrollable, you need to make the page size match the device screen size. e.g. in the file attached in #9, there's no viewport meta tag. This means the default content width is 980 pixels which means the page will be much wider than a typical phone screen. Chrome zooms out when the page is loaded so zooming in allows scrolling around. If you add <meta name="viewport" content="width=device-width"> to that page, the page will be the same size as the device's screen so that it won't load zoomed out and no scrolling is allowed. Does that fix this issue?
,
Jan 2
Thanks for reply, @Bokan : Why changes are required in html page as it is working fine with 50.0.2661.89 but not working with 71.0.3578.98. Thanks
,
Jan 2
I'm not sure what specifically changed here but there's been many changes since M50, perhaps it was a bug fix or one of the changes we made to improve interop with other browsers.
,
Jan 3
Is there any configuration change we can make by that latest google browser will work like 50.0.2661.89 google browser without making change in HTML file. Thanks,
,
Jan 4
Hi, I checked the file you attached #9 on 50.0.2661.89 and it behaves the same way as it does in 72.0.3626.28 - I can scroll around as normal. I think the file attached in #9 references other JS and css files which aren't included. One potential change that's occurred recently is https://www.chromestatus.com/feature/4764225348042752 which caused compat bugs in bug 897906 . In your video, it looks like touches aren't being handled, it's possible script created a handler for touch using ontouch that calls preventDefault on touches, preventing scrolling. If this is the issue, you can fix it (for now - the flag will eventually be removed) by enabling chrome://flags/#touch-events.
,
Jan 10
reporter@ could you attach the page that you can create this issue with so we can double check what the logic is and see what change might have affected that.
,
Jan 17
(5 days ago)
Closing this as there wasn't any feedback from the reporter. Reporter feel free to comment here or file a new bug if you can provide the information reqeusted. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by zebracom...@gmail.com
, Dec 17