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

Bug 346867

Summary: [Preferences] Apply button enabled even if IntegerFieldEditor field is provided an invalid input
Product: [Eclipse Project] Platform Reporter: Harish Garapati <harish.garapati>
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: CLOSED WONTFIX QA Contact:
Severity: minor    
Priority: P3 CC: prakash
Version: 3.6   
Target Milestone: ---   
Hardware: PC   
OS: Windows XP   
Whiteboard: stalebug

Description Harish Garapati CLA 2011-05-23 09:12:40 EDT 
Build Identifier: I20100608-0911

If IntegerFieldEditor field is given an input of invalid value (e.g. string) from the mouse context menu --> Paste, then the Apply button is enabled in the preferences. After clicking on Apply, the error message is getting displayed. The behavior should be the Apply button should be disabled by default whenever an invalid input is provided.
Same is the case with all IntegerFieldEditor fields.

Reproducible: Always

Steps to Reproduce:
1. Open eclipse 3.6 platform
2. Go to Window -> Preferences -> General -> Editors.
3. Copy any string and paste the copied string in "Size of recently opened files list:" field by mouse right click -> Paste.
4. Observe that the Apply button is still enabled and by clicking on Apply, the error message is shown.
5. This is not the case if the paste in step 3 happens by ctrl-v keyboard command. In this case, the error message is shown and the apply button is disabled.
Comment 1 Lars Vogel CLA 2019-11-14 02:21:37 EST 
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.

If the bug is still relevant, please remove the "stalebug" whiteboard tag.