Disabled com.sencha.gxt.widget.core.client.Slider still responds to user interaction.

[dannmartens]

Required Information

Version(s) of Ext GWT
Ext GWT 3.0.1, 3.0.3-SNAPSHOT

Browser versions and OS
(and desktop environment, if applicable)

• Internet Explorer 9, Windows 7
• Firefox 16.0.2, Windows 7
• Chrome 23.0.1271.64 m, Windows 7

Virtual Machine
No

Description
A disabled slider is still responding to user interaction: the slider updates in different ways depending on the style of interaction. Dragging the slider still works in a the disabled state. Clicking anywhere on the guiding gutter consistently generates events, but visually only updates the slider's position erratically.

Run mode
Both development mode, as well as production mode

Steps to reproduce the problem

1. Layout a Slider on a tool bar, position the tool bar in a panel
2. Programatically disable the Slider at creation time, with slider.setEnabled(false); or slider.disable();
3. Open app in browser, verify the disabled state by observing the washed-out color scheme of the slider
4. Interact with the slider's drag handle, by dragging or by clicking anywhere on the slider's guiding gutter

Expected result
The slider should not respond to any user interaction.

Actual result
The slider does respond.

Test case
N/A

Helpful Information

Screenshot or video
N/A

Live test
N/A

Debugging already done
N/A

Possible fix
Unknown

[dannmartens]

On closer inspection, I found out that the:
(1) the apparent erratic behavior of the slider position is caused by an exception escaping from handler code over the event bus. By catching the exception this behavior does not manifest itself. If the exception escapes, the Slider widget does not update itself properly.
(2) The Slider never 'enables', it remains disabled (and visually washed-out).

[dannmartens]

Scratch (2) of my previous remark: that part was caused by a statement which was left behind in error, while fiddling with the configuration. Sorry about that. It does enable when asked.

[Colin Alworth]

Thanks for the report! I have opened a bug in our bug tracker.