w3c / input-events

Input Events
https://w3c.github.io/input-events/
Other
23 stars 16 forks source link

Add event order related to insertFromPaste, fixes #117 #123

Closed johanneswilm closed 2 years ago

johanneswilm commented 2 years ago

Preview | Diff

johanneswilm commented 2 years ago

Hey @saschanaz you tend to be better than me concerning the correct lingo so I have included as a reviewer.

@travisleithead The issue here is that as far as I understand, the decision was that we wanted to say that there should be a paste event whenever we have a insertFromPaste beforeinput event. But we wanted to add this as a non-normative note so that it is just noted as a hint as we are not sure where the entire event order should be defined long-term.

johanneswilm commented 2 years ago

Objective with PR has changed: https://www.w3.org/2021/09/24-editing-minutes.html#a03

I have checked all browsers [1] and the paste event is triggered before the beforeinput event on all four browsers.

[1] https://github.com/johanneswilm/input-events-testing

css-meeting-bot commented 2 years ago

The Web Editing Working Group just discussed do we have a date to discuss #122?.

The full IRC log of that discussion <Travis> Topic: do we have a date to discuss #122?
<Travis> github: https://github.com/w3c/input-events/pull/122
<Travis> BoCupp: I do have a demo to look at this...
<Travis> .. I can paste a link that is a pre-read
<Travis> johanneswilm: I think we need a demo to show the proposal, and to see the problems (as implemented in Safari) and then have a span of time to review the details and form an opinion.
<Travis> .. can we get the demos within the next few weeks before the next meeting?
<Travis> BoCupp: I don't think we need to wait a month.
<Travis> johanneswilm: So we can get a demo shortly?
<Travis> action: BoCupp to provide demo showing potential alternatives and problems for the composition commands
<Travis> github: https://github.com/w3c/input-events/pull/123
johanneswilm commented 2 years ago

@travisleithead should we be migrating from travis to github actions? Or is there another policy in place?