Open zcorpan opened 5 months ago
Interestingly, the event order in Chromium and WebKit is
textInput
and thenbeforeinput
, which maybe should be the other way around for consistency with input from typing.
Gecko's behavior with @masayuki-nakano 's patch for https://bugzilla.mozilla.org/show_bug.cgi?id=903746 is beforeinput
event then textInput
. I've created a PR with a tentative test for this event order: https://github.com/web-platform-tests/wpt/pull/44744
cc @sideshowbarker
See https://github.com/w3c/uievents/pull/362#discussion_r1458219635
https://html.spec.whatwg.org/#drag-and-drop-processing-model defines the drag and drop model and some events, and refers to Pointer Events spec for some events.
When performing a drag and drop operation in an editing host (or dropping in an editing host), browsers fire
textInput
,beforeinput
, mutation events,input
-- which isn't currently defined as far as I can tell.Interestingly, the event order in Chromium and WebKit is
textInput
and thenbeforeinput
, which maybe should be the other way around for consistency with input from typing.Demo: https://software.hixie.ch/utilities/js/live-dom-viewer/saved/11841
I think this should integrate somehow with this part of HTML:
cc @masayuki-nakano