Bug 229800
Summary: | iPad use Magic Keyboard can't scroll | ||
---|---|---|---|
Product: | WebKit | Reporter: | suwe1 <yeshuwei.swy> |
Component: | Scrolling | Assignee: | Nobody <webkit-unassigned> |
Status: | NEW | ||
Severity: | Normal | CC: | simon.fraser, thorton, webkit-bug-importer |
Priority: | P2 | Keywords: | InRadar |
Version: | Other | ||
Hardware: | iPhone / iPad | ||
OS: | iOS 14 | ||
See Also: | https://bugs.webkit.org/show_bug.cgi?id=229390 |
suwe1
you can view the demo I provided through this link:
https://bytedance.feishu.cn/docs/doccnHeiargMGkM9bTN0xahxP6d
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Alexey Proskuryakov
Testing with iOS 15 beta, I see this:
- cannot scroll this page with the keyboard.
- can scroll most of the page with the touchpad, except for the bottom part with a table.
Not quite sure which aspect this report is about. Both work fine on a Mac with 14.1.2.
suwe1
The problem I want to express is that when using iPad Safari, the table at the bottom cannot be scrolled.
You can use this demo to experience this problem. The color block in the demo is the area that cannot be scrolled.
https://d4me0.csb.app/
suwe1
(In reply to Alexey Proskuryakov from comment #1)
> Testing with iOS 15 beta, I see this:
>
> - cannot scroll this page with the keyboard.
> - can scroll most of the page with the touchpad, except for the bottom part
> with a table.
>
> Not quite sure which aspect this report is about. Both work fine on a Mac
> with 14.1.2.
The problem I want to express is that when using iPad Safari, the table at the bottom cannot be scrolled.
You can use this demo to experience this problem. The color block in the demo is the area that cannot be scrolled.
https://d4me0.csb.app/
Simon Fraser (smfr)
This looks the same as bug 229390. It's a very similar test case.
Radar WebKit Bug Importer
<rdar://problem/82919542>
suwe1
(In reply to Simon Fraser (smfr) from comment #4)
> This looks the same as bug 229390. It's a very similar test case.
This is also encountered by our team, but we think it is not the same reason. This problem can also occur in non-Safari 14.1