Bugs realized after the release of Chart Search Module for the reference Application version 1.0 including new presenational features suggested to be added.
created on 01/08/2014
adopted from the feedback held at: https://notes.openmrs.org/ChartSearch-Module-Feedback

    Weight (kg) (kg)  should display one unit

    When count is zero, make checkbox un-clickable

    change the purple background color to match that in the openmrs header

    Don't display any results before the user searches after entering something in the search box like: https://www.google.com/

    Remove support for fuzzy searches based on the Levenshtein Distance which causes a search for "weight" to return "height"

    When searching is going on show some sort of loading progress image i.e giff format

    Response  time to the user should be instantaneous – i.e., when the user types a  search phrase and presses the enter key, respond to the user instantly.   For example, whenever a filter change is applied or a new search is  applied, instantly draw an "Updating results..." box or a big spinner  atop the results pane so both (1) the user perceives the response to be  instantaneous and (2) the user knows when results are being changed.   Watch carefully how the results are updated on kayak.com or orbitz.com  when you change filters on the existing query: a div informing you that  the results are updating appears instantly (less than 50 ms) for any  change to the filters even if the actual results take several seconds  to be fetched.  Even though the results may take 1-3 seconds to appear  (a noticeable delay humans), the user perceives the system as responding instantly.

    No  matter how fast you make Chart Search, factors out of your control will  slow it down in production (e.g., network latency, old clients,  underpowered server, etc.), meaning that searches that take 20 ms in  your development testing may take 3 seconds in some environments.   Nobody will complain about a spinner disappears instantly.  They will  complain or perceive Chart Search as sluggish if they submit a search  and nothing appears to be happening for 750 milliseconds.  Since you're  javascript is already sitting in the browser, there's no reason you  can't respond instantaneously to any user action, even if the actual  results or detail come a little later.

    Clear bug "When no results are found, the result list is blank and the detail pane shows prior results." rather  result list should show something like grey "No results" message and detail pane is blank.

    Focus should start within search box (don't make me click on it first) i.e when the user visits the chart search page, he should immediately without clicking in search box begin typing into the search box

    First  result does not show selection.  If I click on any other result (other  than first in list) it is selected and I can tell because the background  is grey.  When I open Chart Search, the first item is properly  selected, but does not render as if it is selected.

    Hover-driven  selection of filter buttons is distracted.  I would expect a click to  show choice list and another click to dismiss choice list.  If you are  going to use hover, it should apply to the entire button and not just  the label.  My (Burke's) preference would be to make these work like  buttons instead of using hover. see http://i.imgur.com/9ixsjZl.gif

    Still replace hover with onclick here

    Make  category choice label a link that selects that one category, so in the  80% of cases, where I am looking for a specific category,

    Category  choice list renders oddly with wrapping.  It looks like question, test,  and finding are nested & finding label is wrapping to next line  after checkbox

    Categories  button label should change to give an indication of which categories  are selected (e.g., start with "All Categories" and change to selected  category name or list (truncating with "..." if over max chars that fits  neatly in button label)

    de-activated the link on that filter button label to clear "description: If  you scroll down so header is off the top of the browser window and then  click on a filter button label, the page jumps back to the top of the  page.  I would not expect using the filter buttons to affect the  position of the page."

    Support keyboard navigation of results

    Pressing up/down arrows while focus is in the query text box should navigate up/down through results.ok

    When  navigating through selections via the keyboard: (1) wait slightly  longer than the average repeat rate – e.g., 500 ms – before updating  detail in case user is just holding down the arrow key and passing by  results on the way to their target; and (2) avoid blocking on detail  rendering (i.e., even if detail rendering takes 3 seconds, it should not  stop the user from navigating the results... the user should always  perceive their interaction with the result list to be instantaneous)

    Detail  pane shows "(undefined)" in the title for many results (e.g., "Return  visit date (undefined)").  Assuming that it units, it should not be  displayed for non-numeric results.  More specifically, if the value is  undefined, it shouldn't be shown (silently omitted from display).

    non-numeric concepts should hide the graph, instead of showing it empty with "undefined"

    Re-visit obs-groups display,

    Make sure that manually triggering the search by pressing enter means that the delayed auto-search doesn't happen

    Revisit caotegory filtering.

    support custom category definitions

    diagnosis category with obsgroup should return counts and its filter should work well

    Remove the Datatype filter