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 25664 - Nit: DOMString is never defined
Summary: Nit: DOMString is never defined
Status: RESOLVED WONTFIX
Alias: None
Product: Browser Test/Tools WG
Classification: Unclassified
Component: WebDriver (show other bugs)
Version: unspecified
Hardware: All Linux
: P2 normal
Target Milestone: ---
Assignee: Browser Testing and Tools WG
QA Contact: Browser Testing and Tools WG
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 20860
  Show dependency tree / graph
 
Reported: 2014-05-12 20:14 UTC by seva
Modified: 2014-05-12 21:37 UTC (History)
2 users (show)

See Also:

Attachments

Description seva 2014-05-12 20:14:50 UTC 
add a reference to http://www.w3.org/TR/DOM-Level-3-Core/core.html#ID-C74D1578 or somewhere similar?
Comment 1 David Burns :automatedtester 2014-05-12 20:50:01 UTC 
This is already described in 1.4 where it says fragments follow WebIDL. DOMString is described there.
Comment 2 seva 2014-05-12 21:37:15 UTC 
Fair enough, but there are 2 things.

DOMString, when first used (in 2.1 Command), is rendered as "DOMString?" because it is undefined. WebIDL defines "DOMString?" to be the same as "nullable DOMString". That is misleading.

If all mentions of DOMString had a definition it referenced to, it would make it discoverable, too (now section 1.4, reference to WebIDL is not very discoverable for someone who doesn't know what DOMString is and just wants to quickly understand that while reading the spec somewhere in the middle).