[Bug 22057] New: Clarify InputMethodContext's scope in the spec


            Bug ID: 22057
           Summary: Clarify InputMethodContext's scope in the spec
    Classification: Unclassified
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: IME API
          Assignee: mike@w3.org
          Reporter: kochi@google.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, public-webapps@w3.org

An InputMethodContext can be obtained from any HTMLElement, but in some cases
it is unrealistic that all elements in a page have different contexts.

This point is ambiguous in the spec.

For example, consider the following HTML:

<input type=text>
<div contenteditable=true>
  <span id=span1> ... </span>
  <span id=span2> ... </span>

It makes sense <input> and <textarea> can have different context, but
if span1 and span2 can have different contexts, 
 - once cursor enters any of the span, switch to the active context?
 - if selection encompasses 2 <span>s, what context should be activated?

This may complicate the implementation too much.  Probably a guideline

  under one contentable element, all DOM elements under the element
  usually share the same context

makes sense for most implementations.

You are receiving this mail because:
You are on the CC list for the bug.

Received on Thursday, 16 May 2013 08:46:47 UTC