Bug #2918
closedDisabled WPushButton not greyed out with Wt 3.3.2 and theme "polished"?
0%
Description
After upgrading Wt from 3.3.1 to 3.3.2, the disabled pushbuttons are no longer shown as greyed out, but text looks like they are still enabled? I tested with one of the examples from the distribution (socketnotifier), and when setting setCssTheme("polished"), the push button text is still in regular font, even though the button has been disabled. When running the socket notifier example, I modify the createApplication function as here - adding setCssTheme():
Wt::WApplication *createApplication(const Wt::WEnvironment& env)
{
Wt::WApplication *app = new Wt::WApplication(env);
new RssReader(app->root());app->setCssTheme("polished");
return app;
When the notifier is running, the button is disabled, the text changed to "Busy", but still looks enabled, and it can be clicked (there is no callback, but animation active in the web page). See attached screenshot.
It looks like the wt.css file is the correct one from the 3.3.2 distribution, but maybe this is not related to css file?
$ ls -l resources/themes/polished/wt.css
-rw-rw-r--- 1 root root 21189 Apr 2 21:10 resources/themes/polished/wt.css
Any changes in this area - can it be fixed in the CSS file?
Files
Updated by B Sorensen over 10 years ago
Hmmm, after some checks it seems like the problem is with Firefox. It looks ok in Explorer and Chrome, so I'll just do some more checks to identify the exact cause.
Updated by Koen Deforche over 10 years ago
- Status changed from New to InProgress
- Assignee set to Koen Deforche
- Target version set to 3.3.3
Hey,
I just recently noticed this as well, I believe Firefox is giving the wrong priority to CSS rules defined in wt.css instead of it's builtin rules for a disabled button, but this can be worked around.
Regards,
koen
Updated by Koen Deforche over 10 years ago
- Status changed from InProgress to Resolved
Updated by Koen Deforche over 10 years ago
- Status changed from Resolved to Closed