ChromeDevTools / ChromeDevTools/debugger-protocol-viewer
Restore URL-based search functionality
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 893
- Forks
- 188
- Avg merge
- 2d 23h
- Merged PRs (30d)
- 2
Description
One feature that got lost in the rewrite is the ability to permalink search result pages. This also enabled easy searching from within the Chrome address bar (by adding the site as a custom search engine). Let’s restore this functionality!
In terms of URL design, this could be done with a query parameter:
https://chromedevtools.github.io/devtools-protocol/?q=foo
…or with a hash:
https://chromedevtools.github.io/devtools-protocol/#q=foo
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by locating the existing search UI and the page entry point that renders search results. Trace how the current search term is held, then decide whether the query parameter or hash form fits the site; done means a URL can reproduce a search-results page and support Chrome custom-search-engine use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100