Red Hat Bugzilla – Bug 881623
[ALL_LANG][SAM Web GUI] - Visually Disable Button acting as if it is enabled and showing messages
Last modified: 2013-10-01 06:53:54 EDT
Created attachment 654052 [details]
Disabled button acts as an enabled one.
Description of problem:
For all the languages, in the Admin page (Home page --> Admin --> Click on any existing user on the left pane --> Details), the button for "Clear Disabled Helptips" functionality behaving a little odd way when it is disabled.
The first time, when it remains Enabled and user can click to clear. Then, the button text changes from "Clear" to "Cleared" and becomes visually disabled. Ideally it can not be clicked or should not show the same message upon click as like when it was enabled.
But, even after then button is Disabled, first of all, user can click and can also realize that the click action occurred because the message is showing "Disabled Help tips have been re-enabled" following the click action.
Version-Release number of selected component (if applicable):
Subscription Asset Manager Version: 1.2.5-1h.el6_3
Steps to Reproduce:
1. Login in SAM GUI with Admin rights
2. Click on Admin (right-above the home page)
3. Click on any existing user.
4. Click on Enabled "Clear" button on the User "Detail" page.
5. Observe the message showing above and disappears.
6. Now observe the same clear button showing the text "Cleared" instead of
7. Now Again Click on the "Cleared" button.
8. Observe the same message showing again upon every click and disappears.
The button property set wrongly, allowing user to click on it even when it is disable and showing message upon that click action.
No Disabled button should either allow user to click on it/restrict the mouse click/selection option OR it should allow to show any message further upon click.
Additional info: Screen Shot attached.
SNAP0 contains these bug fixes. Moving to ON_QA.
# rpm -qa | grep katello
Disables Buttons do not show the display message and user cannot
click the disabled button
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.