DXR UI Refresh: Difference between revisions

Found out why jruderman needed to load all search results onto the page at once.
(Refactor feedback some more. Rank feedback items by MXR retirement blocking. Add plans & priorities. Move TOC to top.)
(Found out why jruderman needed to load all search results onto the page at once.)
Line 40: Line 40:


* (1) Move to a line-based search, as proposed in https://github.com/mozilla/dxr/pull/161#issuecomment-25201532.
* (1) Move to a line-based search, as proposed in https://github.com/mozilla/dxr/pull/161#issuecomment-25201532.
** This should solve jrudenman's need to sometimes load ''all'' the search results onto the page and then cmd-F through them.
* (2) A way to semantically include double quotes in the search string: the parser shouldn't always eat them.
* (2) A way to semantically include double quotes in the search string: the parser shouldn't always eat them.
* (3) Just typing a filename (or path segment?) without a path: specifier should find files by name or path.
* (3) Just typing a filename (or path segment?) without a path: specifier should find files by name or path.
Line 89: Line 90:
* (4) Direct results: some love them, some hate them (because they just want to see the file pathname (don't we show that with the file? Is it bothersome because it's slow to load?))
* (4) Direct results: some love them, some hate them (because they just want to see the file pathname (don't we show that with the file? Is it bothersome because it's slow to load?))
* (4) Show context around results (with a clickable control? by saying "context:3[lines]" in the query? show the entire statement?)
* (4) Show context around results (with a clickable control? by saying "context:3[lines]" in the query? show the entire statement?)
* A way to load ALL results (other than holding Cmd+Down) (Why? Ask jruderman.)


=== Just Bugs ===
=== Just Bugs ===
Confirmed users
574

edits