Open Bug 1797215 Opened 2 years ago Updated 8 days ago

Send async "touch" events at the widget level instead of synthesized DOM events

Categories

(Remote Protocol :: Marionette, task, P3)

Product:
Remote Protocol
Component:
Marionette
Type:
task
Points:
5

Tracking

(Not tracked)

People

(Reporter: dlrobertson, Unassigned)

References

(Depends on 3 open bugs, Blocks 1 open bug)

Details

(Whiteboard: [webdriver:m15])

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.

Severity: -- → S3
Priority: -- → P2
Whiteboard: [webdriver:backlog]
See Also: → 1785102
Points: --- → 8
Product: Testing → Remote Protocol

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
Points: 8 → 5
Whiteboard: [webdriver:backlog] → [webdriver:m8]
Summary: Consider sending native input touch events → Consider sending widget input events for touch instead of synthesized DOM events
No longer depends on: 1834306
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
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

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]
No longer depends on: 1851812
No longer blocks: 1866500

Note that for calculating the position relative to the top-level widget (browser), you can use the new LayoutUtils.rectToToplevelWidgetRect() helper method. This method allows you to get the target position based on local coordinates, even from within frames. Ensure that the device pixel ratio settings are applied before calling this method.

Depends on: 1904859
Whiteboard: [webdriver:backlog] → [webdriver:m12]

Actually we will try to get this bug done for M12 but decided to mark it as optional.

Priority: P2 → P3
Whiteboard: [webdriver:m12] → [webdriver:m13]
Whiteboard: [webdriver:m13] → [webdriver:m14]
Whiteboard: [webdriver:m14] → [webdriver:m15]
You need to log in before you can comment on or make changes to this bug.