For what its worth, we plan to remove base and extent from Blink/Chromium (
https://code.google.com/p/chromium/issues/detail?id=230267). We've found
that developers do not understand the difference between focus/anchor and
base/extent, and since it is only supported by WebKit based browsers, it
Well stated. I like contentEditable=cursor.
On Mon, Jun 23, 2014 at 9:21 AM, Robin Berjon ro...@w3.org wrote:
On 17/06/2014 02:12 , Julie Parent wrote:
If Intention events are (temporarily) moved out of scope, I think this
leads us back to the question of what would contentEditable
On Fri, Jun 20, 2014 at 8:47 PM, Ryosuke Niwa rn...@apple.com wrote:
On Jun 17, 2014, at 1:44 PM, Julie Parent jpar...@google.com wrote:
On Tue, Jun 17, 2014 at 12:22 PM, Olivier F teleclim...@gmail.com wrote:
On Mon, Jun 16, 2014 at 5:48 PM, Julie Parent jpar...@google.com wrote
On Tue, Jun 17, 2014 at 12:22 PM, Olivier F teleclim...@gmail.com wrote:
On Mon, Jun 16, 2014 at 5:48 PM, Julie Parent jpar...@google.com wrote:
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
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
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
Without default text input, the current proposal for
contentEditable=minimal is essentially just enabling cursors (drawing
them, dispatching events, performing default actions). Rather than calling
the mode minimal, which is ill-defined, why not explicitly call it what
it is: cursor-only? Or,
Have you seen the recent post about the rich text editor that Medium uses?
It is a somewhat cheeky essay, including a mathematical proof, about how
contentEditable is broken. The conclusion is that in order to move
forward, we need to treat contentEditable as an API, rather than as a
standalone
I question whether contentEditable=minimal should actually handle text
input. If the idea is to provide the base platform on which a developer
can build the editing product of their dreams, isn't text insertion just
another behavior they could potentially need to disable?
Stepping back, there
10 matches
Mail list logo
