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 20889 - The src attribute value must be a valid, non-emtpy value, but the next paragraph says that if the url is empty or doesn't resolve Track URL is the empty string. I'm not sure how to interpret this. Sho [...]
Summary: The src attribute value must be a valid, non-emtpy value, but the next paragr...
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-02-06 22:32 UTC by contributor
Modified: 2013-02-06 22:51 UTC (History)
2 users (show)

See Also:

Attachments

Description contributor 2013-02-06 22:32:03 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/
Multipage: http://www.whatwg.org/C#the-track-element
Complete: http://www.whatwg.org/c#the-track-element

Comment:
The src attribute value must be a valid, non-emtpy value, but the next
paragraph says that if the url is empty or doesn't resolve Track URL is the
empty string. I'm not sure how to interpret this. Should I reject <track
src=''> even through the next paragraph makes that unnecessary?

Posted from: 64.213.70.194
User agent: Mozilla/5.0 (X11; Linux x86_64; rv:21.0) Gecko/20130201 Firefox/21.0
Comment 1 Ralph Giles 2013-02-06 22:51:37 UTC 
These are requirements for producers and consumers, respectively, so they're not intended to both constrain the same implementation.

Ian explained on irc, and referred me to http://www.whatwg.org/html/#how-to-read-this-specification