Closed Bug 279926 Opened 20 years ago Closed 14 years ago

readonly textarea does not apply background color if same as CSS:Window

Categories

(Core :: Widget: Win32, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: mikecaines, Unassigned)

References

Details

(Keywords: helpwanted)

Attachments

(2 files)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

If you set the background color of a readonly textarea to the same color as the
CSS 'Window' keyword (i.e. if Window == white), the color is not applied.

Testcase included.

Reproducible: Always

Steps to Reproduce:
1. set Windows XP appearance theme to Windows XP Style: Default (blue)
2. note background color of readonly textarea is gray
3. set style="background-color:white" on readonly textarea
Actual Results:  
Specified background color is not applied

Expected Results:  
Specifed background is applied to the textarea.

- if you change the Window background color in the Windows XP Appearance
properties, the color is applied (since they are no longer the same).

- applying a border style also applies the background color.

- happens in Moz Suite 1.8a6 also
Attached file testcase
Version: unspecified → Trunk
Component: OS Integration → Widget: Win32
Product: Firefox → Core
actually, this would be -moz-appearance overriding the CSS.  if you do
-moz-appearance: none !important it should be fine...
Assignee: bugs → win32
QA Contact: os-integration → ian
This should be fixed in nsNativeThemeWin (or shared?), but I think we also have
a general bug on making nsNativeTheme not be so fragile...
Keywords: helpwanted
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug is still reproducible with Mozilla/5.0 (Windows; U; Windows NT 5.1;
en-US; rv:1.8b5) Gecko/20050925 Firefox/1.4
*** Bug 327494 has been marked as a duplicate of this bug. ***
Status: UNCONFIRMED → NEW
Ever confirmed: true
*** Bug 339016 has been marked as a duplicate of this bug. ***
*** Bug 338887 has been marked as a duplicate of this bug. ***
Assignee: win32 → nobody
QA Contact: ian → win32
Attached file test case
win7:
Mozilla/5.0 (Windows NT 6.1; WOW64; rv:6.0a1) Gecko/20110522 Firefox/6.0a1

XP:
Mozilla/5.0 (Windows NT 5.1; rv:6.0a1) Gecko/20110522 Firefox/6.0a1

WFM
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: