Re: [w3c/editing] [beforeinput] PreventDefault() on InputType=cut differs from Clipboard API (#144)

>> While I can see several solutions working, I think consistency should be important. Without consistency, this will be increasingly difficult to use.

> Yes, but current Clipboard API has a weird default action, where it's like a switch to choose data source.

Indeed. I was thinking more about internal consistency so that beforeinput behaves as similar as possible independently of the inputtype.

> Otherwise they can use `'beforeinput'` to cancel everything and implement it's own single-site clipboard.

Only having a single site site clipboard doesn't sound like a good idea. I don't think anyone does that. What some have been doing is create the single site clipboard in addition to putting things into the system wide clipboard.

How would it look if one wants to add things to the global clipboard? Would that be as I outlined above?

Of course, the cut/copy/paste events don't disappear. So one can still use those as an alternative. I am a little concerned that the beforeinput event for cut will be slightly unusable if it's too difficult to add custom content to the clipboard that way.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/editing/issues/144#issuecomment-240251615