Closed
Bug 31690
Opened 25 years ago
Closed 25 years ago
Send page problem: link & added text unreadable.
Categories
(MailNews Core :: Composition, defect, P3)
MailNews Core
Composition
Tracking
(Not tracked)
People
(Reporter: laurel, Assigned: rhp)
Details
Using 2000-03-13-03-m15-nb1b commercial build on linux rh6.0 Using 2000-03-13-08-m15-nb1b mozilla build on mac OS 9.0 Don't have current win32 build yet. Send page using the url below is received (in seamonkey) with the page link and any user added text unreadable. Same results when sending via plaintext or html compose windows. OK when viewed from 4.x. URL: http://www.discovery.com/exp/mammoth/dispatch.html 1. Browser window open and mail window open. Using IMAP mail account, already authenticated to server. 2. In browser, load the url referenced above, let it finish loading. File|Send Page (to yourself and/or other seamonkey users). 3. Get the message in seamonkey and select it. Wait for downloading to finish. Result: message is displayed with white insert as the compose window from send page. Page link is only partially visible -- looks like we use white text for the link to contrast the page's background and when we overlay the composition area from sending the page this makes the link text unreadable (white on white).
Assignee | ||
Comment 1•25 years ago
|
||
Hi Laurel, This is actually the "Dead Head" bug. The problem we are having is that attached web pages that have color attributes set for that HTML document are changing the webshell for the entire message. In 4.x, we enclosed the attachment in a LAYER and this wouldn't happen. I'll have to see if I can do something similar for SeaMonkey. - rhp *** This bug has been marked as a duplicate of 31052 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Thought it might be a duplicate, but played it safe and logged separately. Marking verified as a duplicate.
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•