Chrome doesn't escape all characters from the URL hash properly for all protocols |
||||||
Issue descriptionURL spec was updated to required escaping of, eg. space inside of fragments here: https://github.com/whatwg/url/pull/347 Mike landed a fix here: https://chromium-review.googlesource.com/c/chromium/src/+/719004 But in Chrome builds with that patch (eg. 65.0.3323.0) I'm still seeing this fail in the associated web-platform-tests, eg: https://w3c-test.org/url/a-element.html The "lolscheme:x x#x x" case reports: assert_equals: href expected "lolscheme:x x#x%20x" but got "lolscheme:x x#x x" Firefox fails for escaping issues outside the fragment: assert_equals: href expected "lolscheme:x x#x%20x" but got "lolscheme:x%20x#x%20x"
,
Feb 2 2018
,
Feb 7 2018
Looks like this test is failing only because it's a non-standard protocol. The hash is escaped properly for http. I'll add an additional test case.
,
Feb 21 2018
Found an existing test case for the http case: https://w3c-test.org/url/a-element.html Parsing: <http://f:21/ b ? d # e > against <http://example.org/foo/bar> Chrome 64 fails with: assert_equals: href expected "lolscheme:x x#x%20x" but got "lolscheme:x x#x x" at Test.<anonymous> (https://w3c-test.org/url/a-element.js:40:7) at Test.step (https://w3c-test.org/resources/testharness.js:1494:25) at test (https://w3c-test.org/resources/testharness.js:511:18) at runURLTests (https://w3c-test.org/url/a-element.js:30:5) at Test.<anonymous> (https://w3c-test.org/url/a-element.js:8:5) at Test.step (https://w3c-test.org/resources/testharness.js:1494:25) And Chrome 65 passes The lolscheme case is still broken though, but that's unlikely to be much of a compat problem in practice so I'll leave this bug open at P3 for that.
,
Feb 21 2018
,
Feb 21 2018
,
Oct 1
mkwst@, are you still working on this? |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by rbyers@chromium.org
, Jan 17 2018