James C Scott III

Thanks for the suggestion @tomayac ! In the short term, we could definitely offer the search button.

@atopal This is the existing issue for the issue you and I were discussing today.

Thanks for the feedback @shalanah! We can definitely add some UI to allow users to change the items per page while also allowing existing users to easily share what page...

Transferring some personal notes I have: - For the mobile sidebar, do what we do in ChromeStatus and have it hover over instead of shifting the page.

There's a mix of tests but not mapped and features without tests. Once we map more features, we can revisit this. Short-term: we could say there are no tests mapped...

The name filter (with or without the `name:` prefix) does a partial string search on both the [name and the id](https://github.com/GoogleChrome/webstatus.dev/blob/main/lib%2Fgcpspanner%2Ffeature_search_query.go#L204). (We call the feature identifier `featurekey` at the database...

Steps: 1. Modify the [FeatureSearch.g4](https://github.com/GoogleChrome/webstatus.dev/blob/main/antlr/FeatureSearch.g4) to add a new term `id`. 2. Run `make gen -B` to regenerate all the generated code 3. Add a new [Identifier](https://github.com/GoogleChrome/webstatus.dev/blob/684a2857d5acd7c15911510c991d5281414f80b5/lib/gcpspanner/searchtypes/searchtypes.go#L88-L97), called `IdentifierID`. -...

Two more things: # Thing 1 we should add a playwright test that always checks that we can support 50 IDs in one query. The test should input the query...

The work for this has been split up into #786 #787 #788

> For sake of transparency features whose status is "not on any standards track" should be shown as such instead of "limited availability" @dmitriid That's a great idea. And it...