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 25410 - Why is zero tokens in rel allowed?
Summary: Why is zero tokens in rel allowed?
Status: RESOLVED WORKSFORME
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: 2014-04-22 12:43 UTC by contributor
Modified: 2014-05-14 12:47 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2014-04-22 12:43:26 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html
Multipage: http://www.whatwg.org/C#attr-link-rel
Complete: http://www.whatwg.org/c#attr-link-rel
Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/

Comment:
Why is zero tokens in rel allowed?

Posted from: 2a00:801:e0:30:514b:81c2:3d3e:2c7d by simonp@opera.com
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/34.0.1847.76 Safari/537.36 OPR/21.0.1432.31 (Edition Next)
Comment 1 Ian 'Hixie' Hickson 2014-04-22 18:24:33 UTC 
Given rel="foo":

   relList.remove('foo');

...leaves an empty rel="". Seems weird that that would be non-conforming.
Comment 2 Simon Pieters 2014-04-22 22:14:52 UTC 
I don't follow. When would you want to do that?
Comment 3 Ian 'Hixie' Hickson 2014-05-13 19:22:21 UTC 
For example in a blog editor, where you're changing the link to have or not have rel=external as the user decides what the link should point to.
Comment 4 Simon Pieters 2014-05-14 12:47:50 UTC 
Hmm. OK.