NEW 274828
REGRESSION (iOS 17.0-17.4?): Zooming and scrolling break on baidu.com
https://bugs.webkit.org/show_bug.cgi?id=274828
Summary REGRESSION (iOS 17.0-17.4?): Zooming and scrolling break on baidu.com
Ali Juma
Reported 2024-05-29 06:11:48 PDT
This was originally reported at crbug.com/342446324 for Chrome on iOS, but also reproduces on other browsers on iOS (I tested on iOS 17.5 in Safari, Firefox, and Edge). This does not reproduce on iOS 17.0 but does on 17.4+. Steps to reproduce: 1) Visit https://baike.baidu.com/reference/1603667/9d2aOhaqcu1GSI-fs51AQzCLGC5YPgcKZrRUpGQE4p-8QgOI1F-nrZ9KhdTKhNTJH_gTeRAxTjE-WFrZSAg 2) Zoom in all the way. 3) Scroll all the way to the bottom. 4) Try to zoom out or scroll back up. At step 4, zooming and scrolling no longer work.
Attachments
Radar WebKit Bug Importer
Comment 1 2024-05-29 09:24:56 PDT
Simon Fraser (smfr)
Comment 2 2024-05-29 11:12:07 PDT
We've been able to reproduce this on iOS 16.6.1 and 17.0. Is it really a regression, or just something the site is doing?
Ali Juma
Comment 3 2024-05-29 11:41:04 PDT
(In reply to Simon Fraser (smfr) from comment #2) > We've been able to reproduce this on iOS 16.6.1 and 17.0. Is it really a > regression, or just something the site is doing? Oh thanks for checking, in that case the site might be doing something weird to trigger this state.
Karl Dubost
Comment 4 2024-05-31 02:06:15 PDT
So fwiw on Firefox Android, and Chrome Android accessing https://baike.baidu.com/reference/1603667/9d2aOhaqcu1GSI-fs51AQzCLGC5YPgcKZrRUpGQE4p-8QgOI1F-nrZ9KhdTKhNTJH_gTeRAxTjE-WFrZSAg We can NOT * scroll * zoom in
Karl Dubost
Comment 5 2024-06-04 00:01:57 PDT
Ali Juma, did you try on Android. Because I tried on Firefox and Chrome and it is even worse there, that might be a site bug to fix.
Ali Juma
Comment 6 2024-06-04 06:15:37 PDT
On Android I can repro extreme slowness but couldn't get to a point where zooming and scrolling are entirely stuck (perhaps getting entirely stuck is device dependent). In any case, the site behaves poorly across browsers so perhaps we should close this as Invalid.
Note You need to log in before you can comment on or make changes to this bug.