[Bug 25405] New: Input Event Types (some correct)

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

            Bug ID: 25405
           Summary: Input Event Types (some correct)
           Product: WebAppsWG
           Version: unspecified
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DOM3 Events
          Assignee: travil@microsoft.com
          Reporter: crimsteam@gmail.com
        QA Contact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, www-dom@w3.org

In table (5.1.1 List of DOM3 Event Types) beforeinput event has this:
Default Action: 
None

But definition beforeinput event has some default action
(https://dvcs.w3.org/hg/dom3events/raw-file/tip/html/DOM3-Events.html#event-type-beforeinput).

Definition table for beforeinput and input should have this (in Context info)

UIEvent.view
UIEvent.detail

All event types implement (or inherit) UIEvent list this property in their
tables. 

And this tables should also include InputEvent.isComposing attribute.

InputEvent.data description in table probably is not complete (when comparing
with HTML5). In HTML5 we have only input event type, and it can be fired
additionally for input type=checkbox/type=radio or select, and in this case
what value is appropriate - empty string or null? On the other hand, HTML5 does
not take into account the InputEvent interface for input event (just inherit
from Event). At now only Firefox started implement this interface (with some
objection due to the HTML5:
https://bugzilla.mozilla.org/show_bug.cgi?id=970802).

According above HTMLSelectElement should be trate as a target for this event
type.

In description for data attribute we have:
[data of type DOMString, readonly
    ...This attribute MAY be null or contain the empty string.]

What exactly means null? If nullable type then definition in interface and
dictionary should have '?' after DOMString (DOMString?).

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

Received on Monday, 21 April 2014 18:42:50 UTC