Closed Bug 1729931 Opened 3 years ago Closed 3 years ago

[wpt-sync] Sync PR 30471 - URLPattern: Throw on more illegal hostname code points.

Categories

(Testing :: web-platform-tests, task, P4)

task

Tracking

(firefox94 fixed)

RESOLVED FIXED
94 Branch
Tracking Status
firefox94 --- fixed

People

(Reporter: mozilla.org, Unassigned)

References

()

Details

(Whiteboard: [wptsync downstream])

Sync web-platform-tests PR 30471 into mozilla-central (this bug is closed when the sync is complete).

PR: https://github.com/web-platform-tests/wpt/pull/30471
Details from upstream follow.

b'Ben Kelly <wanderview@chromium.org>' wrote:

URLPattern: Throw on more illegal hostname code points.

As discussed in the mozilla standards-position issue on URLPattern:

https://github.com/mozilla/standards-positions/issues/566

There are a number of URL encoding interop issues between browsers.
Since URLPattern delegates to the URL parser for canonicalization it
is also exposed to these interop issues.

While fixing all of URL's interop issues is orthogonal to shipping
URLPattern, we can at least prevent clearly illegal code points from
being used in URLPattern. This will avoid increasing usage of these
code points which will in turn make it slightly easier to fix the issue
in the URL parser in the future.

Bug: 1248061
Change-Id: I58a55e4206004a6cba727f19d537c5929ce16d43
Reviewed-on: https://chromium-review.googlesource.com/3152036
WPT-Export-Revision: 85807ff49c2657e13b1287bc94bdf365710a7301

Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/9fdadab32960
[wpt PR 30471] - URLPattern: Throw on more illegal hostname code points., a=testonly
Test result changes from PR not available.
Pushed by wptsync@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/794d43c10bc2
[wpt PR 30471] - URLPattern: Throw on more illegal hostname code points., a=testonly
Test result changes from PR not available.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
Target Milestone: --- → 94 Branch
You need to log in before you can comment on or make changes to this bug.