[Bug 22059] Composition dictionary should be changed

https://www.w3.org/Bugs/Public/show_bug.cgi?id=22059

Takayoshi Kochi <kochi@google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---

--- Comment #13 from Takayoshi Kochi <kochi@google.com> ---
I would like to make clarification - The original proposal[1] says:
> on an element with the contentEditable flag set, then this is the
> starting offset relative to the target's textContent property
> (textContent is a linear view of all the text under an element)

But the current MSDN document[2] (as of today, Dec. 13, 2013) doesn't
mention about behavior when compositionStartOffset/End used in
contenteditable.

The way that a browser generates textContent from DOM tree and
that a browser holds where an IME composition are not usually compatible -
is there really a use case to get offsets within contenteditable?

I personally suppose for contenteditable it is reasonable to return
Range's before and after IME composition within contenteditable
(to different attributes, of course) - but am not sure yet.

What do you think?

[1]
https://dvcs.w3.org/hg/ime-api/raw-file/tip/proposals/IMEProposal.html#widl-InputMethodContext-compositionStartOffset
[2] http://msdn.microsoft.com/en-us/library/ie/dn433247(v=vs.85).aspx

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Friday, 13 December 2013 08:06:11 UTC