14210 2011-09-19 06:49:19 +0000 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. 2012-12-21 14:39:13 +0000 1 1 1 Unclassified WHATWG URL unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#reflecting-content-attributes-in-idl-attributes Blocked on URL spec P3 normal Unsorted 15718 1 contributor annevk annevk erik.arvidsson ian julian.reschke mike public-html-admin public-html-wg-issue-tracking public-webapps zcorpan sideshowbarker+urlspec oldest_to_newest 56968 0 contributor 2011-09-19 06:49:19 +0000 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 56971 1 zcorpan 2011-09-19 06:49:50 +0000 *** Bug 14211 has been marked as a duplicate of this bug. *** 58483 2 ian 2011-10-19 23:37:52 +0000 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. 58535 3 zcorpan 2011-10-20 10:35:46 +0000 In Opera and Firefox, "http://foo bar" is an unresolvable URL. 58853 4 ian 2011-10-25 04:28:20 +0000 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. 63134 5 ian 2012-01-25 23:47:58 +0000 Marking REMIND, please reopen once bug 15718 is resolved. 74773 6 annevk 2012-09-28 10:34:43 +0000 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/