1297248 - [Pointer Event] nsIPresShell::SetCapturingContent doesn't work for setPointerCapture / releasePointerCapture

Status: RESOLVED INVALID

(Core :: DOM: Events, defect, P2)

Description

[Ming-Chou Shih [:stone]]

We call nsIPresShell::SetIsMouseCapturePreventingDrag on parent process while the flag is set via nsIPresShell::SetCapturingContent on child process. We need to

1. let child process send async IPC message to update the flag on parent process
2. let parent process cancel the drag gesture when receiving a request to prevent drag.

Comment 1

[Benjamin Smedberg]

Ming-Chou, can you describe how this would affect users? Do we need this to work across processes, or can we just make this API fail?

Comment 2

[Ming-Chou Shih [:stone]]

Now I only found a problem when pointer event related API using it with flag 'CAPTURE_PREVENTDRAG'. I think this problem wouldn't affect users since pointer event is not shipped yet.

Comment 3

[Hsin-Yi Tsai (she/her)[:hsinyi]]

(In reply to Ming-Chou Shih [:stone] from comment #2)
> Now I only found a problem when pointer event related API using it with flag
> 'CAPTURE_PREVENTDRAG'. I think this problem wouldn't affect users since
> pointer event is not shipped yet.

Hi Stone, could you give an example describing how it would affect user experience? Is it sever that we should treat it as a shipping blocker?

Comment 4

[Hsin-Yi Tsai (she/her)[:hsinyi]]

(In reply to Hsin-Yi Tsai [:hsinyi] from comment #3)
> (In reply to Ming-Chou Shih [:stone] from comment #2)
> > Now I only found a problem when pointer event related API using it with flag
> > 'CAPTURE_PREVENTDRAG'. I think this problem wouldn't affect users since
> > pointer event is not shipped yet.
> 
> Hi Stone, could you give an example describing how it would affect user
> experience? Is it sever that we should treat it as a shipping blocker?

typo: s/sever/severe

Comment 5

[Ming-Chou Shih [:stone]]

The origin problem is that SetCapturingContent doesn't work for the concurrence of pointer lock, dnd, and pointer capture. Now the problem is covered by bug 1399740 and bug 1400792. Closed this one as invalid.