percent-encode U+007F in cannot-be-a-base-URL path and fragment states
According to the URL specification [1], several parts of a parsed url must UTF-8 percent-encoded supersets of the C0 control percent encode set [2]. However, Blink does not do that for U+007F DELETE in the cannot-be-a-base-URL path and fragment states [3] [4]. This CL fixes that and also adds URL WPT tests for various URL percent-encoding cases. You can find more details on the Chrome status entry [5] and intent-to-ship thread [6]. [1] https://url.spec.whatwg.org/#concept-basic-url-parser [2] https://url.spec.whatwg.org/#c0-control-percent-encode-set [3] https://url.spec.whatwg.org/#cannot-be-a-base-url-path-state [4] https://url.spec.whatwg.org/#fragment-state [5] https://chromestatus.com/feature/5651438652882944 [6] https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/en6buycTcKQ Bug: 809852 Change-Id: I9c75224a537f09a5b41ca7e9295f2a3bf7fad061 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2324425Reviewed-by:Mike West <mkwst@chromium.org> Reviewed-by:
Dominick Ng <dominickn@chromium.org> Commit-Queue: Frédéric Wang <fwang@igalia.com> Cr-Commit-Position: refs/heads/master@{#796734}
Showing
Please register or sign in to comment