[Bug 25539] New: Broken links and other correct

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

            Bug ID: 25539
           Summary: Broken links and other 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

I located some broken links and few new fixes.

===

After moving key and code into separate documents, some reference to the keys
are broken. This applies mainly to modifiers (like 'Alt', 'Control', 'Shift',
'Meta', etc.). But first it should be determined if you want use reference or
not for keys, now we have mess (in most case don't use ref for any keys).

In Glossary:
"event order"
"key mapping"
"key value"
"modifier key"

In 
3.5 Activation triggers and behavior
3.5.1 Activation event synthesis
3.5.2 Activation event order

In all event tables [Context (trusted events)] for:
MouseEvent
WheelEvent
KeyboardEvent (including keypress and some descriptions below table like for
keydown)

In 5.2.6.1.1 Attributes 
altKey, ctrlKey and key

In
6.3.4 Input Method Editors (first 'Accept')
Example 35 ('Cancel')
5.2.6.1.2 Methods (link 'Modifier Keys' in table)
5.2.6.2 Keyboard Event Order (last green box 'Tab')

6.1 Keyboard Input (... but briefly describes keyboard layout and... <<    
'keyboard layout' not work)

6.2.1 Motivation for Adding the code Attribute (...refer to as writing system
keys... << 'writing system keys' not work)

6.3 Keyboard Event key Values (...depicted in Figure 4 illustrates one
possible... << 'Figuer 4' not work)

===

You should also labeled keys using title = "". Now you use some background
color for individual cases, but it's difficult to remember what each color
means. With JS it would be very easy, just retrieve elements with specific
classes and set title with a clear description (key value, key code, character
value, glyph).

===

>From 5.2.7.4 to 5.2.7.6 not all of the event names are references (keydown,
compositionstart, compositionend, etc.) but they may be. 

Te same in Example 24 (two tables).

===

5.2.6.1.3 Constants
...Note that the 'NumLock'key should... << missing space 'NumLock'key
...and (other than the 'NumLock'key) did... << missing space 'NumLock'key

===

6.3.2 Modifier keys

For all sequence tables in this section please add headers with descriptions,
something what we have in example 37/38 (including KeyboardEvent.key and
InputEvent.data).

After this every Modifiers can be linked (like in example 37/38).

===

Example 23 and Example 24 << why 'shiftKey' is marked by class="constant-name"?
A little bellow you use class="attribute-name".

And similar, Example 21-24 for key header you used class="key-code", but should
be class="key".

===

And the last, please write something about the future of UI Events spec.:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=25494

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

Received on Saturday, 3 May 2014 02:32:02 UTC