- From: <bugzilla@jessica.w3.org>
- Date: Sat, 18 May 2013 02:16:21 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22082
Bug ID: 22082
Summary: Review and cleanup examples in D3E spec
Classification: Unclassified
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: All
Status: NEW
Severity: normal
Priority: P2
Component: DOM3 Events
Assignee: travil@microsoft.com
Reporter: garykac@google.com
QA Contact: public-webapps-bugzilla@w3.org
CC: mike@w3.org, www-dom@w3.org
The following examples should be updated:
6.1.2 Keyboard Layout
=====================
"If the keyboard layout mapping is switched to a French mapping, pressing the
same key will produce the character 'a' ('\u0041', Latin Capital Letter A)."
The Unicode code point and name are incorrect.
It should read: "... will produce the character 'a' ('\u0061', Latin Small
Letter A)."
6.2.2 Modifier keys
===================
The difference between Examples 1 and 2 (which generate a character) and
Example 3 (which does not) can be made more apparent by adding the
keypress/textinput/beforeinput event to the first 2 examples.
6.2.5 Default actions and cancelable keyboard events
=====================
Third example seems wrong. The keypress should ignore the dead key since it was
canceled. The text describes combining-circumflex + 'e', but the events use é
instead of e. Also, the dead-key was cancelled so the key events should be
simply 'e'.
This example should also be using composition events as described in 5.2.6
6.2.5 Default actions and cancelable keyboard events
=====================
In the second example, step 4, the keypress, should have shiftKey. Actually, we
may want to remove the keypress and replace it with beforeinput.
3.3 Synchronous and asynchronous events
=======================================
In first Example, 'keydown' event is listed, but there is no corresponding
'keyup'. Also, DOMCharacterDataModified has been deprecated and should not be
part of these examples.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Saturday, 18 May 2013 02:16:27 UTC