-
19 Feb 2013 12:46 PM #1
TextButton remains active after clicking
TextButton remains active after clicking
I see there was a fix to clear the active state of a TextButton when the button is detached from the DOM - EXTGWT-2722. But the active state remains if it is not detached, as seen in http://www.sencha.com/examples/#ExamplePlace:buttons under the "Text Only" section. Is this the intended behavior? Since this is not a toggle button I'm not sure why the active state of the button remains.
-
19 Feb 2013 12:47 PM #2
What you are seeing there is probably the indications, that the button is currently focused. Try pressing tab, is the next button blue in that case?
-
19 Feb 2013 12:54 PM #3
Yes, tabbing or clicking away clears the active state of the button. But what is the reason for retaining the active state? In my case I am using a TextButton to save information on a form. Once I click save, I would expect the button to appear the same as before I clicked it, but instead it just appears stuck.
I noticed that the Icon buttons behave the same as TextButton, except that if you click on the icon itself it does clear the active state.
-
19 Feb 2013 1:01 PM #4
This is not really an "active" indicator like when you click it. This means that the button is currently focused and receives keyboard interaction. There is currently no flag to turn that of. The only solution would to a custom ButtonCellAppearance, onFocus needs to be an empty method (no code running)
-
19 Feb 2013 1:39 PM #5
Can you look at http://www.sencha.com/examples/#ExamplePlace:buttons? On any of the buttons that have icons, if you click on the icon itself the blue is cleared once the click is made. This is how I would expect the TextButton to work. However, if you click anywhere other than right on the icon, it does not work as expected...it works just like the TextButtons, where the blue remains.
-
20 Feb 2013 12:29 AM #6
I will move this thread to the bugs forum. It should show the focus indicator regardless on where you clicked.
You found a bug! We've classified it as
EXTGWT-2830
.
We encourage you to continue the discussion and to find an acceptable workaround while we work on a permanent fix.


Reply With Quote