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 14210 - Reflecting href with a URL that doesn't resolve doesn't return the empty string in browsers (at least opera/moz, don't know what URL would fail to resolve in webkit). Instead it returns the value without resolving.
Summary: Reflecting href with a URL that doesn't resolve doesn't return the empty stri...
Status: RESOLVED FIXED
Alias: None
Product: WHATWG
Classification: Unclassified
Component: URL (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Anne
QA Contact: sideshowbarker+urlspec
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard: Blocked on URL spec
Keywords:
: 14211 (view as bug list)
Depends on: 15718
Blocks:
  Show dependency tree / graph
 
Reported: 2011-09-19 06:49 UTC by contributor
Modified: 2012-12-21 14:39 UTC (History)
9 users (show)

See Also:

Attachments

Description contributor 2011-09-19 06:49:19 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/complete/common-dom-interfaces.html
Multipage: http://www.whatwg.org/C#reflecting-content-attributes-in-idl-attributes
Complete: http://www.whatwg.org/c#reflecting-content-attributes-in-idl-attributes

Comment:
Reflecting href with a URL that doesn't resolve doesn't return the empty
string in browsers (at least opera/moz, don't know what URL would fail to
resolve in webkit). Instead it returns the value without resolving.

Posted from: 85.227.155.223 by simonp@opera.com
User agent: Opera/9.80 (Macintosh; Intel Mac OS X 10.5.8; U; en) Presto/2.9.168 Version/11.51
Comment 1 Simon Pieters 2011-09-19 06:49:50 UTC 
*** Bug 14211 has been marked as a duplicate of this bug. ***
Comment 2 Ian 'Hixie' Hickson 2011-10-19 23:37:52 UTC 
Do you have an example of such a URL? The URL parsing section is wrong (e.g. it doesn't lead "::" to being parsed as a relative URL, which Firefox and WebKit seem to agree it is), and so I can't work out what an example of an unparseable URL would be.
Comment 3 Simon Pieters 2011-10-20 10:35:46 UTC 
In Opera and Firefox, "http://foo bar" is an unresolvable URL.
Comment 4 Ian 'Hixie' Hickson 2011-10-25 04:28:20 UTC 
It's not unresolvable per the spec... I think actually everything might be resolvable, now. Which would mean removing the part of the spec that talks about unresolvable ones.
Comment 5 Ian 'Hixie' Hickson 2012-01-25 23:47:58 UTC 
Marking REMIND, please reopen once bug 15718 is resolved.
Comment 6 Anne 2012-09-28 10:34:43 UTC 
http://url.spec.whatwg.org/ defines this per how browsers work. So now all that is needed is that HTML needs to use the definitions from http://url.spec.whatwg.org/