New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Unable to triage subtest #2536

Open

gsnedders opened this issue May 17, 2021 · 2 comments

Assignees

Member

gsnedders commented May 17, 2021

repro:

Load https://wpt.fyi/results/workers/semantics/interface-objects/002.worker.html?label=experimental&label=master&aligned
Enter triage mode
Click on a subtest name
[Nothing happens]

Given subtests can be triaged on a per-browser basis, it should be possible to triage subtests themselves.

KyleJu self-assigned this

KyleJu assigned DanielRyanSmith

Collaborator

KyleJu commented Apr 14, 2022

@foolip Daniel is interested in working on this. My question is that do we have enough use cases for this?

Member Author

gsnedders commented Nov 20, 2024

Use-case: I wanted to link https://wpt.fyi/results/html/dom/idlharness.https.html%3Fexclude=(Document%7CWindow%7CHTML.+)?q=subtest%3A%22navigator%20interface%3A%20attribute%20oscpu%22%20or%20subtest%3A%22navigator%20interface%3A%20operation%20taintenabled%28%29%22&run_id=5194715098251264&run_id=5181332684800000&run_id=5164305890934784 to whatwg/html#10784.

I didn't want to link the entire idlharness test to that issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment