tdierks / doc-history Goto Github PK

The background page for doc-history is unloadable, so each load (which happens silently as the tab is activated/deactivated) will rescan all tabs, possibly create storage writes, and may affect history; also, not sure what activation latency is or whether sync storage can load before we have to start handling keyboard events. Look into making page persistent (RAM/performance tradeoff).

If I have two documents with titles "my doc" and "my fancy doc", where I have accessed "my fancy doc" more recently, and I invoke docs history with [dh my doc], then I will see suggestions with "my fancy doc" ranked higher than "my doc". Then, selecting (by clicking or arrow-key navigation) the entry for "my doc" will result in "my fancy doc" being chosen (as choosing an entry just means completing the search with the title as entry, and "my fancy doc" is a better result then "my doc" for the query [my doc] due to freshness.

Two possible fixes:

1. If there's a way to identify the suggested entry chosen, use that to override ranking.

2. Add an exact-match ranking signal that overrides freshness, so an exact search for [my doc] will match "my doc" over "my fancy doc". Questions:

   • Do this for suggested results, or only for completions? Could be confusing if you enter [my doc] and it chooses a lower suggestion due to exact match.
   • Do it only for exact match, including punctuation and case? This would make list-selection work correctly without changing the search experience much.

The query terms split into "a", "(b/c)": first, not sure if this is right; then, the problem is that after being converted to a regexp with a leading "\b", /\b(b/c)/" doesn't match because \b won't match before "(" in "a (" (the space-parentheses boundary is not a word boundary).

Look into whether we can/should provide a default when no query (populate with most-recently-used docs, maybe filtered to ones not already open?)

To reproduce:

• invoke doc-history
• type a little until you see some options
• click on one
• observe: nothing happens
• should: navigate

If you use doc-history to navigate to a doc which is already open in another tab, we should activate that tab instead of opening another one. Consider identifying such docs on the completion menu as well.