Bug 8269

Summary: REGRESSION: disabled text field does not display greyed-out text
Product: WebKit Reporter: Chris Petersen <c.petersen87>
Component: FormsAssignee: Adele Peterson <adele>
Status: VERIFIED FIXED    
Severity: Normal Keywords: InRadar, Regression
Priority: P1    
Version: 420+   
Hardware: Mac   
OS: OS X 10.4   
Attachments:
Description Flags
Input text element with disabled attribute
none
patch darin: review-

Chris Petersen
Reported 2006-04-08 17:05:00 PDT
Input text fields that use the disabled attribute don't display their content as dimmed or grey. With Safari 2.0.3, input fields that use the disabled attribute display it's text content with a grey value. * STEPS TO REPRODUCE 1. With TOT Webkit, load the test case "input_disabled.html" 2. Notice the text displayed in the text field is displayed as black. 3. This text should be grey to indicate the field as disabled. * REGRESSION Yes, this works in Safari 2.0.3.
Attachments
Input text element with disabled attribute (252 bytes, text/html)
2006-04-08 17:07 PDT, Chris Petersen 		no flags
Details
patch (25.51 KB, patch)
2006-04-17 14:41 PDT, Adele Peterson 		darin: review-
DetailsFormatted DiffDiff
View All Add attachment proposed patch, testcase, etc.
Chris Petersen
Comment 1 2006-04-08 17:07:47 PDT
Created attachment 7588 [details] Input text element with disabled attribute
Chris Petersen
Comment 2 2006-04-08 17:09:13 PDT
This has been filed as <rdar://problem/4507660>
Adele Peterson
Comment 3 2006-04-17 14:41:01 PDT
Created attachment 7778 [details] patch
Adele Peterson
Comment 4 2006-04-17 14:49:03 PDT
Comment on attachment 7778 [details] patch there are still a few more layout tests that I'll need to update
Darin Adler
Comment 5 2006-04-17 17:32:38 PDT
Comment on attachment 7778 [details] patch I gave Adele a bunch of comments in person and she's working on a new patch.
Adele Peterson
Comment 6 2006-04-17 23:37:46 PDT
Darin reviewed an updated fix.
Chris Petersen
Comment 7 2006-04-20 23:02:34 PDT
Verified with latest TOT Webkit build (r13990).
Note You need to log in before you can comment on or make changes to this bug.