This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 25408 - Small typos
Summary: Small typos
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: HISTORICAL - DOM3 Events (show other bugs)
Version: unspecified
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Gary Kacmarcik
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-04-21 22:33 UTC by Arkadiusz Michalski (Spirit)
Modified: 2014-04-27 17:15 UTC (History)
3 users (show)

See Also:


Attachments

Description Arkadiusz Michalski (Spirit) 2014-04-21 22:33:45 UTC
In mouseup def

https://dvcs.w3.org/hg/dom3events/raw-file/tip/html/DOM3-Events.html#event-type-mouseup

we have green box:

"Authoring Note: In some implementation environments, such as a browser, a mouseup event can be dispatched even if the pointing device has left the boundary of the user agent, e.g., if the user began a drag operation with a mouse button pressed)." << closing parenthesis, but no opening.

====

https://dvcs.w3.org/hg/dom3events/raw-file/tip/html/DOM3-Events.html#interface-WheelEvent

IDL for WheelEventInit and it's description use 0.0, but in even wheel attributes we see just 0. Should be used one convention.

====

You should check links in all IDL def, because now a lot of not work:
- const in Event, WheelEvent
- method stopPropagation(), preventDefault(), stopImmediatePropagation()
- and much more

====

In IDL def we have space between method name and '(' - is intentional? DOM and HTML5 never use them, maybe better would be use the same convention.
Comment 1 Arkadiusz Michalski (Spirit) 2014-04-22 10:46:53 UTC
In glossary we have defined 'hysteresis' but you never link to them. This term is used in:
- Event Order (https://dvcs.w3.org/hg/dom3events/raw-file/tip/html/DOM3-Events.html#events-mouseevent-event-order)
- click (https://dvcs.w3.org/hg/dom3events/raw-file/tip/html/DOM3-Events.html#event-type-click)

A reference to this term would be appropriate.

The same for 'rotation', never link to them but this term exist in some "Wheel Event Types" descriptions. I'm not excluded that may be more, I would recommend thoroughly check each term in source code (relative to their id) and make correct.

A similar class of adjustment (in glossary)
- 'delta' description has WheelEvent interface but without ref to WheelEvent.	
- "event listener" description has (in green box) EventListener, Event and handleEvent but without ref.
- 'un-initialized value' has Event but without ref.
Comment 2 Arkadiusz Michalski (Spirit) 2014-04-25 14:25:55 UTC
In glossary 'text composition system' should be after 'target phase'.

====

Any plans to change ref of DOM3 Core to DOM4(W3C)/DOM(WHATWAG), like in 'document' term (https://dvcs.w3.org/hg/dom3events/raw-file/tip/html/DOM3-Events.html#glossary-document) and maybe some other places?
Comment 3 Arkadiusz Michalski (Spirit) 2014-04-25 17:59:57 UTC
And similar in glossary:
- 'key value' should be after 'key mapping'
- 'capture phase' and 'character value' should be after 'candidate event handlers|candidate event listeners'
Comment 4 Gary Kacmarcik 2014-04-27 17:15:05 UTC
extra closing paren - FIXED remove close paren

WheelEventInit - FIXED changed to be 0.0 everywhere

for the IDL links - FIXED:
* The IDL constants in the respec-generated code were not getting correct hrefs. I've updated fixup.js to correct these so they should all be working now.
* stopImmediatePropagation was not working because my fixup script wasn't (apparently) waiting long enough before fixing up the respec generated code. I've made it wait longer and this seems to work consistently. Note that this won't be a problem for the final version since we'll have statically generated html.
* for some other methods, the signature was changed (eg: AbstractView -> Window) so they were no longer being cleaned up. This has been fixed.
Note that console log errors should be reported when the script is unable to fixup everything it expects to do.

IDL space between name and '(' - This is autogenerated by respec, we don't have a space there in the original source.  All respec-based specs should have this as well.

glossary terms:
hysteresis - FIXED
rotation - Not all the 'rotation's in the text map to this term, but I've FIXED the ones that should
delta - FIXED
EventListener/handleEvent - FIXED
un-initialized - FIXED (changed 'Event' to generic 'event')

alphabetic order for glossary - FIXED

Re: change ref to DOM3 Core. There has been no discussion of that, but if you feel it should be changed, please open a bug for that so that we can discuss it.



https://dvcs.w3.org/hg/dom3events/rev/94e701e465ee
https://dvcs.w3.org/hg/dom3events/rev/18f90bc297a4