Bug 196816

Summary:	[testcase][HTML 4 Conformance] A disabled HTML button element should look dimmed, grayed out
Product:	[Applications] konqueror	Reporter:	Gérard Talbot (no longer involved) <browserbugs2>
Component:	khtml	Assignee:	Konqueror Bugs <konqueror-bugs-null>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	dominik.tritscher, rakuco
Priority:	NOR	Keywords:	testcase, triaged
Version First Reported In:	4.13.1
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
URL:	http://www.gtalbot.org/BrowserBugsSection/Konqueror4Bugs/disabled-button-dimmed.html
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Gérard Talbot (no longer involved) 2009-06-17 00:12:04 UTC

Version:           Konqueror (using KDE 4.2.4)
OS:                Linux
Installed from:    Ubuntu Packages

Testcase:
http://www.gtalbot.org/BrowserBugsSection/Konqueror4Bugs/disabled-button-dimmed.html

Expected results: A disabled HTML button element should be very easy to distinguish from an enabled HTML button element. A disabled HTML button element should look dimmed, grayed out.

When viewing/comparing an enabled input form control and a disabled input form control, we can clearly, easily distinguish the enabled one from the disabled one.

Actual results in Konqueror 4.2.4: there is no visual distinction whatsoever between a disabled HTML button element and an enabled HTML button element.

Reference: disabled: When set for a form control, this boolean attribute disables the control for user input. (...) it cannot receive user input
 coming from HTML 4.01, section 17.12.1 Disabled controls

An excellent meta-testcase webpage: Robin Lionheart HTML 4 Conformance test: Forms:
http://www.robinlionheart.com/stds/html4/forms

Note: "(...) to tweak the CSS some more to grey out the font"
coming from 
https://bugs.kde.org/show_bug.cgi?id=170159#c2
Maksim Orlovich

regards, Gérard

Comment 1 Dominik Tritscher 2009-06-21 16:03:56 UTC

Confirmed on trunk r984009.

Comment 2 Christoph Cullmann 2024-05-06 18:38:51 UTC

Dear user,

KHTML (and KJS) was a long time more or less unmaintained and got removed in KF6.

Please migrate to use a QWebEngine based HTML component.

We will do no further fixes or improvements to the KF5 branches of these components beside important security fixes.

For security issues, please see:

https://kde.org/info/security/

Sorry that we did not fix this issue during the life-time of KHTML.

Greetings
Christoph Cullmann