Closed Bug 1953756 Opened 1 months ago Closed 1 month ago

[wpt-sync] Sync PR 51316 - URLPattern: correct port and hostname-related test

Categories

(Core :: CSS Parsing and Computation, task, P4)

Product:
Core
Component:
CSS Parsing and Computation
Type:
task

Tracking

()

Status:
RESOLVED FIXED
Milestone:
138 Branch
Tracking Flags:
Tracking Status
firefox138 --- fixed

People

(Reporter: wpt-sync, Unassigned)

References

(
URL
)

Details

(Whiteboard: [wptsync downstream])

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

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

Anne van Kesteren <annevk@annevk.nl> wrote:

URLPattern: correct port and hostname-related test

For https://github.com/whatwg/urlpattern/issues/260 (port) and https://github.com/whatwg/urlpattern/issues/252 (hostname).

This is what I get after I patch WebKit. I don't really understand the outcomes for the https://{sub.}?example{.com/}foo test though. Primarily because I have a hard time reading the URLPattern parser. I was hoping you could verify with your implementation @anonrig and hopefully @sisidovski can deduce it from the specification.

(This does not depend on https://github.com/whatwg/url/pull/863. That's only for existing tests with a : in the hostname.)

PR 51316 applied with additional changes from upstream: ae2959e7314b2280910216fb43ba55016ed8074e, 3b6b19853a928ec9bfa28e9046c3cf601f160e42, 827d52cc6e31939974f91cda7c0c77ef61d4444b
Component: web-platform-tests → CSS Parsing and Computation
Product: Testing → Core
The PR was not expected to affect any tests, but the try push wasn't a success. Check the try results for infrastructure issues
Pushed by wptsync@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/9dbcbd2b2e87 [wpt PR 51316] - URLPattern: correct port and hostname-related test, a=testonly
Test result changes from PR not available.

https://hg.mozilla.org/mozilla-central/rev/9dbcbd2b2e87

Status: NEW → RESOLVED
Closed: 1 month ago
status-firefox138: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 138 Branch
You need to log in before you can comment on or make changes to this bug.