- From: Ben Peters <Ben.Peters@microsoft.com>
- Date: Thu, 5 Jun 2014 18:36:00 +0000
- To: Julie Parent <jparent@google.com>
- CC: public-webapps <public-webapps@w3.org>
On Thu, Jun 5, 2014 at 11:16 AM, Julie Parent <jparent@google.com> wrote:
> Custom commands are definitely a key concept, and I agree with them. What
> would the transition from the current execCommand signature look like? aka,
> execCommand(String aCommandName, Boolean aShowDefaultUI, String
> aValueArgument). I think ShowDefaultUI may not even be used by anyone, and
> could be removed (we'd need to verify this obviously)? For commands that
> currently take an argument for the value, would you just convert to
> document.execCommand('FormatBlock', {value:'h1'})?
Unfortunately, ShowDefaultUI is used for createLink. So I believe we should support both
execCommand(String aCommandName, Boolean aShowDefaultUI, String aValueArgument)
and
execCommand(string aCommandName, object commandData)
Received on Thursday, 5 June 2014 18:36:31 UTC