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 21787 - Setting <area>.href to a relative URL should set the content attribute to the listeral value instead of resolved value, to match browsers and what the spec requires for other reflecting URL attributes [...]
Summary: Setting <area>.href to a relative URL should set the content attribute to the...
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-04-23 13:32 UTC by contributor
Modified: 2016-01-24 05:34 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2013-04-23 13:32:09 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-map-element.html
Multipage: http://www.whatwg.org/C#the-area-element
Complete: http://www.whatwg.org/c#the-area-element
Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/

Comment:
Setting <area>.href to a relative URL should set the content attribute to the
listeral value instead of resolved value, to match browsers and what the spec
requires for other reflecting URL attributes (and what the spec required
before adopting URLUtils)

Posted from: 90.230.217.68
User agent: Opera/9.80 (Macintosh; Intel Mac OS X 10.8.3) Presto/2.12.388 Version/12.15
Comment 1 Ian 'Hixie' Hickson 2013-04-23 15:36:19 UTC 
HTML doesn't define .href anymore. Reassigning to URL. Anne, if this should be fixed in HTML, let me know how I should do it. Thanks!
Comment 3 Ian 'Hixie' Hickson 2013-06-05 20:25:21 UTC 
This broke Location.href instead. The update steps for Location.href need to be passed an absolute URL, since the URL is immediately used to navigate.

Reassigning to Anne so he can decide how we should fix this. :-)
Comment 4 contributor 2013-06-05 20:26:42 UTC 
Checked in as WHATWG revision r7908.
Check-in comment: Update to match recent URL spec changes (this fixes a.href/area.href, but note that this breaks Location.href instead; see the bug for details)
http://html5.org/tools/web-apps-tracker?from=7907&to=7908
Comment 5 Anne 2013-06-06 13:31:38 UTC 
I don't see how that's true. You pass the value to assign() or replace() which both parse it relative to a base URL just fine.
Comment 6 Domenic Denicola 2016-01-24 05:34:22 UTC 
I believe this has been fixed as of the recent overhaul of URL, Location, and HTMLHyperlinkUtils.