Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 390205

Summary: Unreadable font in search dropdown
Product: [ECD] Orion Reporter: John Arthorne <john.arthorne>
Component: ClientAssignee: libing wang <libingw>
Status: RESOLVED FIXED QA Contact:
Severity: normal    
Priority: P3 CC: libingw
Version: unspecified   
Target Milestone: 1.0 RC1   
Hardware: PC   
OS: Windows 7   
Whiteboard:
Attachments:
Description Flags
Screen shot none

Description John Arthorne CLA 2012-09-24 10:15:45 EDT 
I20120921-1702

I can't read the font in the dropdown that shows recent searches. The size is small, but it also seems to be using a different font face for the "saved searches" part.
Comment 1 John Arthorne CLA 2012-09-24 10:16:14 EDT 
Created attachment 221415 [details]
Screen shot
Comment 2 Susan McCourt CLA 2012-09-24 13:10:13 EDT 
I think the searchbox font itself is about as small as we can get away with, so making it smaller in the autocomplete is getting unreadable.

Maybe changing the layout of saved searches in the popup would help.  For example, we could stack the name of the saved search and description of it vertically.  This would also help show that it's different, and perhaps we wouldn't need the parenthetical "saved search" at all.

So instead of

foo          'foo' in Orion Client (saved search)

we'd have
foo
   'foo' in Orion Client

Another idea is headings in the autocomplete

Recent
  faz
  foo
  fuu
Saved
  foo - 'foo' in Orion Client
Comment 3 libing wang CLA 2012-09-24 14:06:15 EDT 
Seems that the html5 "datalist" binding to the "input" (*http://www.w3schools.com/html5/tag_datalist.asp) is not quite fitting our needs yet. Given that Safari 5 and IE 9 do not support datalist at all, we may want to think about making the proposal UI from scratch.
Comment 4 libing wang CLA 2012-09-27 22:01:33 EDT 
fixed with http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=9ff10f438717d105d852c32cf6612a8038f78dba.
Now we have home grown input completion support.
The global search is the first consumer of it.

I am thinking about consuming it in local search as well.