[
https://issues.apache.org/jira/browse/JSPWIKI-920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dave Koelmeyer updated JSPWIKI-920:
-----------------------------------
Attachment: JSPWiki-FullSearch-1.png
JSPWiki-FullSearch-2.png
JSPWiki-FullSearch-3.png
Screengrabs attached illustrating the behaviour described in sequence.
> HADDOCK: full search should default to a full search
> ----------------------------------------------------
>
> Key: JSPWIKI-920
> URL: https://issues.apache.org/jira/browse/JSPWIKI-920
> Project: JSPWiki
> Issue Type: Improvement
> Components: Templates and UI
> Affects Versions: 2.10.2
> Environment: Client is:
> - Firefox 40 (Ubuntu 14.04).
> Server is:
> - JSPWiki v2.10.2-svn-38 running in GlassFish v4
> - Container managed authentication is enabled using a file-based realm
> - HTTPS is enabled
> - JSPWiki policy is locked down such that only authenticated users have
> access (both read and write)
> Reporter: Dave Koelmeyer
> Attachments: JSPWiki-FullSearch-1.png, JSPWiki-FullSearch-2.png,
> JSPWiki-FullSearch-3.png
>
>
> Not sure if this is a bug as such, but if not then the default behaviour
> could be changed. To reproduce:
> 1) User enters a search term into the dynamic search field. JSPWiki prompts
> "For full search, hit enter...". The user presses Enter.
> 2) On the screen that appears, no search results are found, because the
> search query has not actually been executed.
> 3) If the user then presses "Find!", the search query is executed and results
> are displayed.
> Step 3) should be the default behaviour after the user performs step 1), and
> step 2) should be used to refine search results if needed. At present there
> is an unnecessary extra step.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)