https://www.w3.org/Bugs/Public/show_bug.cgi?id=8
Ms2ger ms2...@gmail.com changed:
What|Removed |Added
Status|RESOLVED|REOPENED
CC|
Hi, Art–
Following on from the discussion at the AC, here is my suggested wording:
[[
Robust Anchoring API
Defines APIs for finding, addressing, and linking to a document
selection based on a set of selectors, even when the document has
changed. This may be a joint deliverable with the
There's been a good deal of discussion about the value of
contentEditable=minimal. Some of us think that being able to cancel all browser
actions with preventDefault on all Intention events is enough, while others
believe that having a single way to stop browsers from taking action makes
[ Was: Re: [charter] Addressable Ranges? ]
Doug proposes WebApps include a Robust Anchoring API in its charter and
this is a CfC to do so. The specific proposed addition is below and it
includes this API being a joint spec with the proposed Web Annotations
WG (draft charter is [1]).
If you
If Intention events are (temporarily) moved out of scope, I think this
leads us back to the question of what would contentEditable='minimal' do
exactly? Enable collapsed selections and default handling of cursor
movement ... anything else? If this is all it would do, then perhaps what
we really
On Mon, Jun 16, 2014 at 5:12 PM, Julie Parent jpar...@google.com wrote:
If Intention events are (temporarily) moved out of scope,
I don’t think I’d say they’re out of scope, just that they will likely not be
ready as quickly as we could do contentEditable=’minimal’. Do you agree with
that?
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
On Mon, Jun 16, 2014 at 5:23 PM, Ben Peters ben.pet...@microsoft.com
wrote:
On Mon, Jun 16, 2014 at 5:12 PM, Julie Parent jpar...@google.com wrote:
If Intention events are (temporarily) moved out of scope,
I don’t think I’d say they’re out of scope, just that they will likely not
be ready
On Mon, Jun 16, 2014 at 5:48 PM, Julie Parent jpar...@google.com wrote:
Yes. I really like the idea of explicitly enabling what you want and of
separating the concepts. Being able to turn on commandEvents independent of
a cursor seems useful. An API like this leaves far fewer questions of
