Re: Should minimal contentEditable default text input

2014-06-06 Thread Robin Berjon
On 30/05/2014 08:25 , Anne van Kesteren wrote: On Fri, May 30, 2014 at 12:50 AM, Julie Parent jpar...@gmail.com wrote: Or, rather than tying this concept to contentEditable, with all the assumptions and complications that brings up, why not expose this building block as a completely separate

Re: Should minimal contentEditable default text input

2014-06-06 Thread Robin Berjon
On 30/05/2014 00:50 , Julie Parent wrote: 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

Re: Should minimal contentEditable default text input (was: contentEditable=minimal)

2014-06-06 Thread Ryosuke Niwa
On May 29, 2014, at 3:50 PM, Julie Parent jpar...@gmail.com wrote: 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

Re: Should minimal contentEditable default text input (was: contentEditable=minimal)

2014-06-06 Thread Ryosuke Niwa
On May 26, 2014, at 1:25 AM, Anne van Kesteren ann...@annevk.nl wrote: On Mon, May 26, 2014 at 4:17 AM, Yoshifumi Inoue yo...@chromium.org wrote: To implement text composition with this, I would like to have wave underline, dotted underline, thick underline etc. Range.prototype.style seems

Re: Should minimal contentEditable default text input (was: contentEditable=minimal)

2014-05-30 Thread Anne van Kesteren
On Fri, May 30, 2014 at 12:50 AM, Julie Parent jpar...@gmail.com wrote: Or, rather than tying this concept to contentEditable, with all the assumptions and complications that brings up, why not expose this building block as a completely separate attribute? Just a DOM API perhaps as you're not

Re: Should minimal contentEditable default text input (was: contentEditable=minimal)

2014-05-29 Thread Julie Parent
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,

Re: Should minimal contentEditable default text input (was: contentEditable=minimal)

2014-05-26 Thread Anne van Kesteren
On Mon, May 26, 2014 at 4:17 AM, Yoshifumi Inoue yo...@chromium.org wrote: Range.style is cool idea! I assume Range.detach() removes styles added Range.style. detach() is a no-op. http://dom.spec.whatwg.org/#dom-range-detach To implement text composition with this, I would like to have wave

Re: Should minimal contentEditable default text input

2014-05-26 Thread Robin Berjon
On 26/05/2014 10:25 , Anne van Kesteren wrote: On Mon, May 26, 2014 at 4:17 AM, Yoshifumi Inoue yo...@chromium.org wrote: Range.style is cool idea! I assume Range.detach() removes styles added Range.style. detach() is a no-op. http://dom.spec.whatwg.org/#dom-range-detach You're jumping in

Re: Should minimal contentEditable default text input (was: contentEditable=minimal)

2014-05-25 Thread Yoshifumi Inoue
Range.style is cool idea! I assume Range.detach() removes styles added Range.style. To implement text composition with this, I would like to have wave underline, dotted underline, thick underline etc. Example:: http://www.w3.org/TR/2012/WD-ime-api-20120524/images/image13.png Also, we can use

Should minimal contentEditable default text input (was: contentEditable=minimal)

2014-05-23 Thread Robin Berjon
Starting a new thread for this specific topic as I think it's one of the important early points of contention. On 22/05/2014 12:59 , Piotr KoszuliƄski wrote: 3. Typing characters. It works in textarea and I think it should work out of the box in cE=minimal. Otherwise, cE=minimal will be