Hi @KyleJu, I would like to work on this issue. Just to clarify, we should only need to modify webapp/components/test-search.js right?

Hi @KyleJu, I would like to work on this issue. Just to clarify, we should only need to modify webapp/components/test-search.js right?

Yup It is likely a frontend issue and webapp/components/test-search.js should be the place

Hi, I want to check my understanding of the search box.

Right now the search box supports two functions:

1. Parse a search into the required structured query object using Ohm to pass into the api/search endpoint.
2. Navigate to a given file-path. E.g. Entering /encoding/encodeInto.any.html should navigate you to the results for that test. (this process is actually automatic and does not require a query commit)

Side-notes:

• In webapp/components/test-search.js, how does value="{{ queryInput::input }}" work? From my understanding, this is equivalent to having an oninput listener that does this.queryInput = e.target.value and that this is a virtual method call, but I can't find where the input method is binded.
• For the navigation/auto-complete function, it involves a lot of querySelector calls and code-coupling with webapp/components/wpt-results.js and webapp/components/wpt-app.js. Is there a better way to perform this operation?

I ran into this now when trying to search for "enumerateDevices" tests for web-platform-tests/interop#532. The UI keeps changing it to "enumeratedevices" which doesn't find anything. Editing the URL does work though:
https://wpt.fyi/results/?label=master&label=experimental&aligned&q=%28path%3A%2Faudio-output%20or%20path%3A%2Fmediacapture-streams%29%20enumerateDevices

@KyleJu can you take a look at #3577?