Bug 42538 - [JFace] Number fields should have reasonable size
Summary: [JFace] Number fields should have reasonable size
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 42229 (view as bug list)
Depends on:
Blocks:
 
Reported: 2003-09-04 11:13 EDT by Andre Weinand CLA
Modified: 2019-09-06 16:07 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Andre Weinand CLA 2003-09-04 11:13:31 EDT 
Number fields should be only as wide as it is necessary for the accepted value range.
If number fields automatically extend to the width of their container, they look like string input 
fields and may confuse users.

Examples are:
- local history preference page
- workbench preference page
- editors preference page
- build order preference page
- debug console preference page
- debug launch history
- help server preference
- install/update preference
- java debug preference
- team CVS preference page
- team preference page
- go to line dialog
Comment 1 Tod Creasey CLA 2003-09-04 11:30:53 EDT 
*** Bug 42229 has been marked as a duplicate of this bug. ***
Comment 2 Tod Creasey CLA 2004-04-15 08:49:00 EDT 
Not for 3.0
Comment 3 Tod Creasey CLA 2004-06-28 11:28:18 EDT 
Reopening now that 3.0 has shipped
Comment 4 Susan McCourt CLA 2007-06-29 13:02:07 EDT 
This message is part of a mass update on bugs that have been reviewed for several releases, but not fixed.  The bug is legitimate, but not a priority.  Marking P5.  Patches would be entertained.
Comment 5 Susan McCourt CLA 2009-07-09 15:31:18 EDT 
As per http://wiki.eclipse.org/Platform_UI/Bug_Triage_Change_2009
Comment 6 Eclipse Webmaster CLA 2019-09-06 16:07:40 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.