Open
Bug 1797215
Opened 2 years ago
Updated 5 months ago
Send async "touch" events at the widget level instead of synthesized DOM events
Categories
(Remote Protocol :: Marionette, task, P2)
Remote Protocol
Marionette
Tracking
(Not tracked)
NEW
People
(Reporter: dlrobertson, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Whiteboard: [webdriver:backlog])
Many of the scrollend and overscroll event tests use touchScrollInTarget to trigger a scroll in a scrollable element. Use native touch events instead of DOM events to make it possible to use touchScrollInTarget-like patterns in tests.
|
||
Updated•2 years ago
|
Severity: -- → S3
Priority: -- → P2
Whiteboard: [webdriver:backlog]
|
|
||
Updated•1 year ago
|
Points: --- → 8
|
||
Updated•1 year ago
|
Product: Testing → Remote Protocol
|
|
||
Comment 1•1 year ago
|
||
Touch events are a special type of events so I assume this should be blocked on bug 1773393 instead.
No longer blocks: parent-actions
status-firefox111:
--- → fixed
status-firefox112:
--- → fixed
status-firefox113:
--- → fixed
status-firefox-esr102:
--- → fixed
Depends on: parent-actions
|
|
||
Updated•1 year ago
|
status-firefox111:
fixed → ---
status-firefox112:
fixed → ---
status-firefox113:
fixed → ---
status-firefox-esr102:
fixed → ---
|
|
||
Updated•8 months ago
|
Blocks: parent-actions
No longer depends on: parent-actions
|
|
||
Updated•8 months ago
|
Points: 8 → 5
Whiteboard: [webdriver:backlog] → [webdriver:m8]
|
|
||
Updated•8 months ago
|
Summary: Consider sending native input touch events → Consider sending widget input events for touch instead of synthesized DOM events
|
|
||
Updated•7 months ago
|
Summary: Consider sending widget input events for touch instead of synthesized DOM events → Send async touch events at the widget level instead of synthesized DOM events
|
|
||
Updated•7 months ago
|
Summary: Send async touch events at the widget level instead of synthesized DOM events → Send async "touch" events at the widget level instead of synthesized DOM events
|
|
||
Comment 2•7 months ago
|
||
Please note that with bug 1852243 we have a temporary workaround available that will work fine for layout folks to work towards the interop 2023 goals. As such we do not have to work on this feature in M8 anymore.
Whiteboard: [webdriver:m8] → [webdriver:backlog]
You need to log in
before you can comment on or make changes to this bug.
Description
•