23461 2013-10-08 16:17:12 +0000 Strip leading slashes? 2014-01-13 18:23:06 +0000 1 1 1 Unclassified WHATWG URL unspecified All All RESOLVED WORKSFORME P2 normal Unsorted 1 erik.arvidsson annevk mike santi sideshowbarker+urlspec oldest_to_newest 94473 0 erik.arvidsson 2013-10-08 16:17:12 +0000 Both WebKit/Blink and Gecko strip leading slashes when setting hostname. IE throws. a = document.createElement('a'); a.href = 'http://abc.de:8080/path/name?search#hash' a.hostname = '///xyz'; assert(a.href === 'http://xyz:8080/path/name?search#hash') I'm also fine throwing in cases like these but we should specify what the intended behavior is. 94752 1 annevk 2013-10-15 12:32:49 +0000 So you parse using http://url.spec.whatwg.org/#hostname-state as override state. It will lead to "host" being the empty sequence which will lead to the host parser returning failure which means the parse operation will return failure. Which means host remains unchanged. 94753 2 annevk 2013-10-15 12:35:06 +0000 Note that ignoring invalid values is consistent with eg: a.hostname = "a a" 94765 3 erik.arvidsson 2013-10-15 14:22:37 +0000 In cases like these. Are we trying to spec what browsers do or what we want them to do? If we are making changes I think I would prefer us to follow IE in these cases and throw instead of silently ignoring. 98282 4 annevk 2014-01-11 16:53:52 +0000 I'm not sure that specifying what IE does make sense. E.g. if I try a = document.createElement("a") a.href = "http://example" a.hostname = "a:a" IE does not throw. But if I then read a.hostname it throws. Do we really want to define that? For most other cases we silently ignore errors. Starting to throw could cause more breakage in sites. Apple is typically extremely hesitant to switch from non-throwing to throwing as well. 98346 5 annevk 2014-01-13 18:23:06 +0000 Ignore was fine in bug 23474 too.