Bug 140080

Summary: Location object attributes shouldn't be decoded?
Product: WebKit Reporter: Jonathan Zuckerman <j.zuckerman>
Component: DOMAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: annevk, ap, kandalkar.abhijeet58
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   

Description Jonathan Zuckerman 2015-01-05 07:08:46 PST
I might be making some leaps here, or using terminology wrongly, but I think the correct behavior for the Location object is to return a valid URI or URI components in the Location object attributes,

"The value of the href attribute MUST be the absolute URI reference"
http://www.w3.org/TR/Window/#location

and the percent character by itself (not as part of a uri-encoded octet) is not a valid character in a uri,

"Because the percent "%" character always has the reserved purpose of being the escape indicator, it must be escaped as "%25" in order to be used as data within a URI."
https://www.ietf.org/rfc/rfc2396.txt (page 9)

Currently `location.href` will return a decoded version of the url (percent-encoded values will be decoded), is this the correct behavior according to the standards?
Comment 1 Anne van Kesteren 2023-12-29 03:14:01 PST
That's not correct, but that's also no longer happening.