On 17/06/2014 02:39 , Julie Parent wrote:
I certainly understand the concern that it would be impossible to
properly catch and cancel all events. But I think that is somewhat the
point - it forces browser vendors to get these parts right. All changes
to an editable dom must fire an event before
On Jun 17, 2014, at 9:00 AM, Piotr Koszuliński
wrote:
>
> On Tue, Jun 17, 2014 at 2:39 AM, Julie Parent wrote:
> I certainly understand the concern that it would be impossible to properly
> catch and cancel all events.
>
> I'm not concerned only about this. I'm concerned about the fact that
On Tue, Jun 17, 2014 at 2:39 AM, Julie Parent wrote:
> I certainly understand the concern that it would be impossible to properly
> catch and cancel all events.
>
I'm not concerned only about this. I'm concerned about the fact that
currently existing commands and editable-related features does n
I certainly understand the concern that it would be impossible to properly
catch and cancel all events. But I think that is somewhat the point - it
forces browser vendors to get these parts right. All changes to an
editable dom must fire an event before the modifications are made, and must
be can
On Sun, Jun 15, 2014 at 5:15 AM, Olivier F wrote:
>
> On Fri, Jun 13, 2014 at 11:37 AM, Ben Peters
> wrote:
>
>> On Fri, Jun 13, 2014 at 1:01 AM, Ryosuke Niwa wrote:
>> >> On Jun 12, 2014, at 5:07 PM, Olivier F wrote:
>>
>> >> Imagine as well a situation where a UA creates a new way to paste
>
On Fri, Jun 13, 2014 at 11:37 AM, Ben Peters
wrote:
> On Fri, Jun 13, 2014 at 1:01 AM, Ryosuke Niwa wrote:
> >> On Jun 12, 2014, at 5:07 PM, Olivier F wrote:
>
> >> Imagine as well a situation where a UA creates a new way to paste
> content, and to prevent confusion with "paste" they decide to
On Fri, Jun 13, 2014 at 1:01 AM, Ryosuke Niwa wrote:
>> On Jun 12, 2014, at 5:07 PM, Olivier F wrote:
>>
>> I have been reading this and have a comment:
>> http://w3c.github.io/editing-explainer/commands-explainer.html
>>
>> "Issue 11: We may not need contentEditable=minimal. The same thing can b
On Jun 12, 2014, at 5:07 PM, Olivier F wrote:
> I have been reading this and have a comment:
> http://w3c.github.io/editing-explainer/commands-explainer.html
>
> "Issue 11: We may not need contentEditable=minimal. The same thing can be
> accomplished by listening for commands and calling preve
I have been reading this and have a comment:
http://w3c.github.io/editing-explainer/commands-explainer.html
"Issue 11: We may not need contentEditable=minimal. The same thing can be
accomplished by listening for commands and calling preventDefault on all of
them."
I think we need contentEditable=
On Jun 6, 2014, at 6:27 AM, Robin Berjon wrote:
> On 28/05/2014 01:39 , Julie Parent wrote:
>> The discussion of which minimal default handling to include with
>> contenteditable="minimal" makes me wonder if contentEditable="minimal"
>> is necessary at all. It quickly becomes a can of worms of
On 28/05/2014 01:39 , Julie Parent wrote:
The discussion of which minimal default handling to include with
contenteditable="minimal" makes me wonder if contentEditable="minimal"
is necessary at all. It quickly becomes a can of worms of *which*
default handling should be included, and it seems li
a site would want to handle themselves, we don’t
> need CE Min as a feature, only a concept that can achieved with
> preventDefault().
>
> From: Julie Parent [mailto:jpar...@gmail.com]
> Sent: Tuesday, May 27, 2014 4:40 PM
> To: Ben Peters
> Cc: public-webapps@
:40 PM
To: Ben Peters
Cc: Julie Parent; public-webapps@w3.org
Subject: Re: [editing] CommandEvent and contentEditable=minimal Explainer
But what is the "default" behaviour then? What will we be preventing? There's
no accepted specification for current contentEditable=true AFAIK, so
chieved with
> preventDefault().
>
>
>
> *From:* Julie Parent [mailto:jpar...@gmail.com]
> *Sent:* Tuesday, May 27, 2014 4:40 PM
> *To:* Ben Peters
> *Cc:* public-webapps@w3.org
> *Subject:* Re: [editing] CommandEvent and contentEditable=minimal
> Explainer
>
>
>
gmail.com]
Sent: Tuesday, May 27, 2014 4:40 PM
To: Ben Peters
Cc: public-webapps@w3.org<mailto:public-webapps@w3.org>
Subject: Re: [editing] CommandEvent and contentEditable=minimal Explainer
The discussion of which minimal default handling to include with
contenteditable="minimal
: Tuesday, May 27, 2014 4:40 PM
To: Ben Peters
Cc: public-webapps@w3.org
Subject: Re: [editing] CommandEvent and contentEditable=minimal Explainer
The discussion of which minimal default handling to include with
contenteditable="minimal" makes me wonder if contentEditable="minimal"
The discussion of which minimal default handling to include with
contenteditable="minimal" makes me wonder if contentEditable="minimal" is
necessary at all. It quickly becomes a can of worms of *which* default
handling should be included, and it seems likely to not satisfy every use
case no matter
17 matches
Mail list logo
