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 15752 - base.href shouldn't reflect the content attribute normally. It needs to be resolved against the document's URI *before* <base> is applied; otherwise "foo/" resolves to "http://whatever/foo/foo/" instead of "http://whatever/foo/".
Summary: base.href shouldn't reflect the content attribute normally. It needs to be r...
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: 2012-01-27 19:37 UTC by contributor
Modified: 2013-04-26 12:38 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2012-01-27 19:37:22 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/semantics.html
Multipage: http://www.whatwg.org/C#the-base-element
Complete: http://www.whatwg.org/c#the-base-element

Comment:
base.href shouldn't reflect the content attribute normally.  It needs to be
resolved against the document's URI *before* <base> is applied; otherwise
"foo/" resolves to "http://whatever/foo/foo/" instead of
"http://whatever/foo/".

Posted from: 72.229.29.65
User agent: Mozilla/5.0 (X11; Linux i686) AppleWebKit/535.19 (KHTML, like Gecko) Chrome/18.0.1017.2 Safari/535.19
Comment 1 Aryeh Gregor 2012-01-27 19:37:33 UTC 
See Gecko bug: https://bugzilla.mozilla.org/show_bug.cgi?id=600809
Comment 2 contributor 2012-07-18 08:00:52 UTC 
This bug was cloned to create bug 18009 as part of operation convergence.
Comment 3 Ian 'Hixie' Hickson 2012-08-24 18:45:01 UTC 
This change moves the spec towards what Opera and Firefox do (more towards what Firefox does).
Comment 4 Silvia Pfeiffer 2013-04-26 12:38:00 UTC 
FYI: fixed in commit 7266