Closed
Bug 99649
Opened 23 years ago
Closed 22 years ago
Body tag graphic relic appears when switching from Preview view to Show all tags view
Categories
(SeaMonkey :: Composer, defect)
SeaMonkey
Composer
Tracking
(Not tracked)
mozilla1.0.1
People
(Reporter: TucsonTester2, Assigned: cmanske)
References
Details
Attachments
(1 obsolete file)
After switching from "Preview" to "Show All Tags" view composer has what appears to be a second body tag (actually a graphic relic) showing in the show all tags view. Build: 2001091003 Reproducibility: Everytime Steps to Reproduce: 1.Open Composer 2.Switch to Preview view 3.Switch to Show All Tags view Actual Results: A second body tag will appear to show up behind the real one. This is not a real body tag but something that appears there. Expected Results: I would expect that only one body tag would appear no matter what view I switch from.
Comment 1•23 years ago
|
||
-->glazman Daniel--this seems like a duplicate of bug #88681 but that is resolved fix. Any ideas? Is this a regression?
Assignee: brade → glazman
Not sure it is a regression... More probably, yet another occurence of a problem caused by the BodyFixupRule :-( Ok, I keep this bug but with a 1.0 target; Cc:ing hyatt too.
Status: UNCONFIRMED → ASSIGNED
Ever confirmed: true
Updated•23 years ago
|
Target Milestone: --- → mozilla1.0
hyatt: yet another BodyFixupRule pb imho...
Comment 4•23 years ago
|
||
Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 (you can query for this string to delete spam or retrieve the list of bugs I've moved)
Target Milestone: mozilla1.0 → mozilla1.0.1
Comment 5•23 years ago
|
||
*** Bug 122469 has been marked as a duplicate of this bug. ***
Comment 6•22 years ago
|
||
*** Bug 130957 has been marked as a duplicate of this bug. ***
Duplicate of bug 63863?
Assignee | ||
Comment 9•22 years ago
|
||
ok, I have made a CSS workaround for this bug (that Charley just attached above). It's only a workaround ; the repaint problem hidden behind is still there but at least it makes happy Composer users.
Assignee | ||
Comment 11•22 years ago
|
||
Since fix is in Composer, I'll take the bug. Fix is by glazman.
Assignee: dbaron → cmanske
Assignee | ||
Comment 12•22 years ago
|
||
Comment on attachment 74348 [details] [diff] [review] Fix r=cmanske
Attachment #74348 -
Flags: review+
Assignee | ||
Updated•22 years ago
|
Comment 13•22 years ago
|
||
Please don't resolve this bug after checking in that workaround (unless dbaron sees that it is a duplicate of bug 63863. This bug is about an issue which we are going to mask but the problem is still there. My preference would have been to file a new bug with this workaround patch (or reopen a duplicate bug) but leave this bug intact and assigned to dbaron.
Assignee | ||
Comment 14•22 years ago
|
||
I'd say this is just another symptom of bug 63863, thus fixing this doesn't get dbaron off the hook for fixing actual problem. I don't see the need for any other bug.
The patch on bug 63863 fixes this bug.
Assignee | ||
Updated•22 years ago
|
Whiteboard: FIX IN HAND,need sr=
Comment 16•22 years ago
|
||
So is this to be closed dupe of 63863 or do you still need sr= on the patch here?
Comment 17•22 years ago
|
||
I am not seeing this problem anymore. Should this be resolved as a dupe of bug 63863? Or should it be resolved as WORKSFORME? Or do you guys want to keep this open for tracking purposes?
Comment 18•22 years ago
|
||
Comment on attachment 74348 [details] [diff] [review] Fix obsoleting hacky patch
Attachment #74348 -
Attachment is obsolete: true
Comment 19•22 years ago
|
||
dupe *** This bug has been marked as a duplicate of 63863 ***
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•