Closed Bug 264506 Opened 20 years ago Closed 19 years ago

Unable to change Background page colour and image in composer

Categories

(SeaMonkey :: Composer, defect)

Product:
SeaMonkey
Component:
Composer
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED EXPIRED

People

(Reporter: mchintag, Unassigned)

Details

Attachments

(1 file)

The patch fixes the bug
2.74 KB, patch
Details | Diff | Splinter Review 
User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; FunWebProducts; .NET CLR 1.1.4322)
Build Identifier: 

Cant change the background color and image once it is set for the first time. 


Reproducible: Always
Steps to Reproduce:
1.Open the browser
2.Open an Existing HTML document in composer
3.Open the Format menu and click on Page color and Background option.
4.It opens the page Color and Background dialog.
5.Select "Use custom colors" option and specify color for text links and 
background.
6.Click on OK button of the dialog. 

Actual Results:  
Use Custom Colors option is not working as per the selections. For the first 
time the Normal Text is changed but it cannot be changed for the next time. 
Even the background is not changing for the first time.



Expected Results:  
The page appears with the chosen properties of color.
The parameters from the dialog are not copied properly through 
globalElement.setAttributes. The patch attached will allow the do this
properly.
Related to/duplicate of bug 239476?
Yes, except the patch in this bug fixes some additional removeAttribute callers.

Reporter, could you make a patch against current trunk?
Product: Browser → Seamonkey
I think the problems initially reported in the bug were fixed by Bug 239476
(text color and bgcolor). Starting with a new page, those are the only
attributes set via CSS. alink, link, and vlink are always set on the <body> tag.
In addition, the "Page Colors and Background" dialog doesn't seem to recognize
the css equivalents (a:link, a:visited, etc.) when importing a page which has
these already set. Even if I change all the alink, link, and vlink calls to be
setAttributeOrEquivalent, it doesn't change the CSS properties.
I am running into the same problem of not being able to change the background
color from the color that the page opened with. I must save before I exit and
doing so reverts the page back to the origional colors. I also tried to edit the
page colors using the html code and was unsuccessful. It does appear that the
color changes will take one per session, but you are unable to change colors
after that until you close completely and reopen, but I can't tell if that is a
fluke or something else.
Using Linux, Mozilla Composer ver 1.7.2 (Suse Linux package).  Problem
experienced is exactly as described.
I wouldn't bother testing this (or anything else, really) with 1.7.x builds...
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 has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: