Closed Bug 67848 Opened 25 years ago Closed 24 years ago

background-color wrong for readonly textfield

Categories

(SeaMonkey :: Themes, defect, P2)

x86
Linux
defect

Tracking

(Not tracked)

VERIFIED FIXED
mozilla0.9

People

(Reporter: moz_user, Assigned: hewitt)

References

Details

(Keywords: modern)

From Bugzilla Helper: User-Agent: Mozilla/4.72 [en] (X11; U; Linux 2.4.0-test10 i686) BuildID: Mozilla 0.7 and buildID 2001020608 The background-color for read-only textfield widgets should be light blue for the MODERN theme. Reproducible: Always Steps to Reproduce: 1.Create XUL window with the following widgets: <textfield id="foo1" value="ok to edit"/> <textfield id="foo2" value="can't edit" readonly="true"/> 2.Launch Mozilla and display the XUL Actual Results: foo2 is displayed with a white (#FFFFFF) background-color Expected Results: foo2 should be displayed with a light blue (#B4C3D4) background-color This is only a problem with the MODERN theme. The classic and blue themes display readonly textfields with a #CCCCCC background-color. The background-color defined for the .textfield-internal-box and .textarea-internal-box style is overriding the one defined for textfield[readonly="true"]. SOLUTION: Delete the background-color attribute in the .textfield-internal-box and .textarea-internal-box styles
Status: NEW → ASSIGNED
Priority: -- → P2
Summary: background-color wrong for readonly textfield (modern only) → [Modern] background-color wrong for readonly textfield
Target Milestone: --- → mozilla0.9
FYI: That's not the correct solution. Need to define the following styles: textfield[readonly="true"] .textfield-internal-box, textfield[readonly="true"] .textarea-internal-box
Keywords: modern
Summary: [Modern] background-color wrong for readonly textfield → background-color wrong for readonly textfield
Depends on: 65745
fixed
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Marking verified on linux (2001-03-22-19-Mtrunk).
Status: RESOLVED → VERIFIED
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.