Open
Bug 2051461
Opened 15 days ago
Updated 8 days ago
Implement a mock drag service for parent process mouse event dispatching
Categories
(Remote Protocol :: Agent, task, P3)
Remote Protocol
Agent
Tracking
(Not tracked)
ASSIGNED
People
(Reporter: hiro, Assigned: hiro)
References
(Blocks 3 open bugs)
Details
(Whiteboard: [webdriver:m21] [webdriver:external])
Attachments
(1 file)
No description provided.
|
Assignee | |
Comment 1•15 days ago
|
||
Mouse events that WebDriver synthesizes asynchronously are injected in the
parent process and have no native drag-and-drop loop, so a drag started by them
leaked the content BrowserChild drag session (intermittent
MOZ_ASSERT(!sourceSession)).
With such a drag now taking the normal cross-process path and being owned by
the parent process, register the mock drag service in the parent when a drag
may start, drive dragover/drop through MockDragServiceController from the
WebDriver action layer, and end the session at action-chain finalize via
ChromeUtils.endDragSession().
|
||
Updated•15 days ago
|
Assignee: nobody → hikezoe.birchill
Status: NEW → ASSIGNED
|
||
Updated•13 days ago
|
Blocks: parent-actions, 1998347
Summary: Implement the mock of dran service for parent process mouse event dispatching → Implement a mock drag service for parent process mouse event dispatching
|
||
Updated•8 days ago
|
Priority: -- → P3
Whiteboard: [webdriver:m21] [webdriver:external]
You need to log in
before you can comment on or make changes to this bug.
Description
•