The pointerevents/idlharness.https.window.html test should not require the presence of onpointerrawupdate

[rr-codes]

Test List

https://wpt.fyi/pointerevents/idlharness.https.window.html

Rationale

WebKit does not plan on supporting onpointerrawupdate at this time. Additionally, it is still currently an experimental feature. Because of these reasons, we believe idlharness.https.window.html should be updated to pass even if onpointerrawupdate is not supported.

[nt1m]

cc @mustaqahmed @flackr @EdgarChen @smaug---- @masayuki-nakano

[smaug----]

pointerrawupdate is in the spec https://w3c.github.io/pointerevents/ https://w3c.github.io/pointerevents/#extensions-to-the-globaleventhandlers-mixin

[nt1m]

We might be able to try to implement pointerrawupdate.

[masayuki-nakano]

FYI: I tried to implement pointerrawupdate on Firefox, but I got some unclear points.

• Clarify the event target of pointermove if an event listener of the preceding pointerrawupdate explicitly release pointer capture w3c/pointerevents#509
• Clarify whether pointermove will be dispatched if pointerrawupdate listener removes the document w3c/pointerevents#510
• Shouldn't dispatch gotpointercapture and lostpointercapture events if pointerrawupdate event is fired without the following pointermove? w3c/pointerevents#511