Skip to content
This repository was archived by the owner on Apr 12, 2024. It is now read-only.

New docs power-search does not search under 4 characters #3078

Closed
ProLoser opened this issue Jun 27, 2013 · 2 comments
Closed

New docs power-search does not search under 4 characters #3078

ProLoser opened this issue Jun 27, 2013 · 2 comments

Comments

@ProLoser
Copy link
Contributor

If I type in a search under 4 characters in the new site-search bar, and hit [return] nothing happens. This is also unhelpful when trying to locate short directives such as ngIf or the anchor tag.

Instead, if you have under 4 characters and [return] IS hit, a search should explicitly be performed if a new search results page does not become the new solution.

In addition, if you hit return, the first(?) result is automatically opened, but there is no visual feedback to tell users which item this is or which item will be chosen.

@jeffbcross
Copy link
Contributor

+1, I thought search was broken when searching for $q

@Narretz
Copy link
Contributor

Narretz commented Feb 23, 2014

sort of still relevant, even if the power search now searches starting with 3 chars and when you hit enter the search result overlay closes.

jarrettch added a commit to jarrettch/angular.js that referenced this issue Mar 7, 2014
Searching for the anchor tag directive doesn't work when searching "a" but searching "q" returns $q as a result.
petebacondarwin added a commit that referenced this issue May 16, 2014
When the search input box was submitted (i.e. by pressing enter) the
app was supposed to take you to the first item but this was not happening.
It turns out the app was just reading the wrong property for the path to
the item.

Closes #3078
petebacondarwin added a commit that referenced this issue May 16, 2014
With the minimum search length set to 3, it was not possible to search for `$q`.
Changing this to 2 fixes that without really upsetting the search display, since we
only display the first 40 API and 14 non-API items anyway.

Closes #3078
petebacondarwin added a commit that referenced this issue May 16, 2014
When the search input box was submitted (i.e. by pressing enter) the
app was supposed to take you to the first item but this was not happening.
It turns out the app was just reading the wrong property for the path to
the item.

Closes #3078
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants