Bug 1029779 - Holding backspace will jump to other input field.
Summary: Holding backspace will jump to other input field.
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Installer
Version: 6.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Thomas Hauser
QA Contact: Petr Kremensky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-13 08:12 UTC by Petr Kremensky
Modified: 2017-10-10 00:26 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-18 14:14:11 UTC
Type: Bug

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

Description Petr Kremensky 2013-11-13 08:12:08 UTC 
Description of problem:
 I run into this on Socket Binding screens. Holding backspace will jump from "Default Value" input field into "System Property field" so user can unintentionally remove some part of System property variable. 

Version-Release number of selected component (if applicable):
 EAP 6.2.0.ER7

How reproducible:
 Always

Steps to Reproduce:
 1. Run gui installer. Go to Socket Bindings screen using default values.
 2. Choose to Configure custom port bindings, at least one of domain/standalone mode, and press Next .
 3. Navigate to some "Default value" field and hold backspace.

Actual results:
 Once the default value is empty the cursor will jump to "System Property field" and continue with deleting.

Expected results:
 Cursor will stay in "Default value" field.

Additional info:
 If this is the intended behaviour feel free to close this one.
Comment 1 Thomas Hauser 2013-11-15 15:29:22 UTC 
This behavior is how IzPack was designed, but we may want / need to change it or make it configurable in IzPack xml descriptors. Marking for later release since the impact is low.
Comment 2 Thomas Hauser 2013-11-18 14:14:11 UTC 
We can re-open this if we want to look at it for a later release.
Note You need to log in before you can comment on or make changes to this bug.