- From: Johannes Wilm <notifications@github.com>
- Date: Tue, 19 Nov 2019 01:03:38 -0800
- To: w3c/editing <editing@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 19 November 2019 09:04:13 UTC
@masayuki-nakano If you want to, you can add something to the `execCommand` spec about it. That document is not expected to move beyond draft status and anything `execCommand` related can go in there. I don't have an opinion on whether a beforeinput event should or should not be triggered when `execCommand` is executed and whether that event then is cancelable or not, as it's irrelevant for the JavaScript editors that are out there. For the resizing issue: This resizing feature is disabled by default now, right? So unless JavaScript reenables it using `execCommand` or the user enables it in the browser configuration, it is off - correct? If my assumption is correct, and given that this is a feature that is only still there because a small number of Firefox users are using it in an intranet app somewhere, I would argue it's ok not to add it to the spec. But I would also be ok with adding it there as long as it's something the user can trigger by doing things in the browser and not just programmatically through `execCommand`. -- 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/200#issuecomment-555403189
Received on Tuesday, 19 November 2019 09:04:13 UTC