On Sat, Sep 6, 2014 at 1:54 AM, Johannes Wilm wrote:
> These both look quite good!
>
> On Example 3 on the commands explainer, I was wondering if it is the idea
> that custom actions only can be triggered by specific key presses, whereas
> for standard events are triggered by "intentions". So sa
I think what I'm hearing in this conversation about the shape of a new
contentEditable is really that a simple "minimal" is not going to work.
Instead, having something like a delimited list will satisfy more people. See
the bug on GitHub [1] for more details.
https://github.com/w3c/editing-exp
I agree that we can divide this work, but so far I think we should do "2"
first. Being able to remove browser functionality with a simple API is going to
be far quicker to implement (in browsers) and provides immediate benefit.
Solving Intentions will be a longer process, but is also important t
Selection.extend is a separate API from Selection.modify. They are both listed
by Mozilla at
https://developer.mozilla.org/en-US/docs/Web/API/Selection?redirectlocale=en-US&redirectslug=DOM%2FSelection
for reference. Thanks for the feedback!
Ben
From: e...@ictenablers.com [mailto:e...@ictenabl
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26852
Bug ID: 26852
Summary: [Custom]: Specify preference of localName and
typeExtension in createElement
Product: WebAppsWG
Version: unspecified
Hardware: PC
O
