- From: <bugzilla@jessica.w3.org>
- Date: Mon, 01 Sep 2014 02:20:43 +0000
- To: www-dom@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26699 Bug ID: 26699 Summary: Some clean up Product: WebAppsWG Version: unspecified Hardware: PC OS: Windows NT Status: NEW Severity: normal Priority: P2 Component: DOM Assignee: annevk@annevk.nl Reporter: crimsteam@gmail.com QA Contact: public-webapps-bugzilla@w3.org CC: mike@w3.org, www-dom@w3.org I collect some small fixes: === In [Each NodeIterator object has these removing steps with oldNode, oldParent, and oldPreviousSibling:] 2. >Set the referenceNode attribute to firs.... << remove this ">" sign. The same algo in 2.2, 2.4 we see "terminate these steps", but maybe better use "terminate these substeps", and change green box "Steps are not terminated here." to "Substeps are not terminated here." We have this in "invoke the event listeners" http://dom.spec.whatwg.org/#concept-event-listener-invoke === In Element.closest(selectors): http://dom.spec.whatwg.org/#dom-element-closest 2. For each element in elements, if match a selectors string selectors against element returns true, return element, . << this "," before "." can be remove. === Maybe add some info that NamedNodeMap are always live (like some Collections). We have this info in previous spec: http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-1780488922 http://www.w3.org/TR/DOM-Level-2-Core/core.html#ID-1780488922 The same is for DOMTokenList, but this is new in DOM. === In 3.3 Error names http://dom.spec.whatwg.org/#dom-element-hasattributes INUSE_ATTRIBUTE_ERR (9) << should be INUSE_ATTRIBUTE_ERR (10) === In algo "remove an attribute by name" and "remove an attribute by namespace and local name": 2. If attr is non-null, remove it from element's attribute list. << just use "from element", because "remove" algo do it later. http://dom.spec.whatwg.org/#concept-element-attributes-remove-by-name http://dom.spec.whatwg.org/#concept-element-attributes-remove-by-namespace === In Document interface: http://dom.spec.whatwg.org/#interface-document Attr createAttribute(DOMString localName); change to [NewObject] Attr createAttribute(DOMString localName); and Attr createAttributeNS(DOMString namespace, DOMString name); change to [NewObject] Attr createAttributeNS(DOMString? namespace, DOMString name); The same in Element interface: http://dom.spec.whatwg.org/#interface-element Attr? getAttributeNodeNS(DOMString namespace, DOMString localName); change to Attr? getAttributeNodeNS(DOMString? namespace, DOMString localName); === In "validate and extract" algo: http://dom.spec.whatwg.org/#validate-and-extract all "name" variable should be "qualifiedName" (step 5., 8. and 9.). === Maybe use new [Exposed] syntax in DOM too? https://github.com/whatwg/url/commit/d59c1ade1684a68b64f868de819b22459467ef96 http://heycam.github.io/webidl/#dfn-extended-attribute === How we can deduce from IDL, that some interface are not available in global. Look: callback interface NodeFilter << have access (and example we can read constant) callback interface EventListener << don't have access There exist some extended attribute that inform about this? Maybe [NoInterfaceObject] do this? === Why in table for Document.createEvent(interface): http://dom.spec.whatwg.org/#dom-document-createevent we have [UIEVENTS] ref for some events, not [DOM3EVENTS]? And why TouchEvent don't reffer to any spec (is markered)? -- You are receiving this mail because: You are on the CC list for the bug.
Received on Monday, 1 September 2014 02:20:46 UTC