nsObjectFrame's PaintSelf call does the wrong thing for paint layers

RESOLVED WORKSFORME

Status

()

RESOLVED WORKSFORME
14 years ago
5 months ago

People

(Reporter: dbaron, Assigned: dbaron)

Tracking

({css1})

Trunk
mozilla1.8beta2
x86
Linux
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [patch])

Attachments

(2 attachments, 2 obsolete attachments)

nsObjectFrame's PaintSelf call does the wrong thing for paint layers.

Testcase to come later, but patch now, so I don't lose it.
Created attachment 180687 [details] [diff] [review]
patch

This obviously isn't tested very well yet.

Perhaps we should put this display check inside of PaintSelf itself.  It'll
mean calling it more, but I maybe that's OK.
Status: NEW → ASSIGNED
Whiteboard: [patch]
Target Milestone: --- → mozilla1.8beta2
Actually, we may want to drop the PaintSelf completely due to the shared style
contexts.  And I don't think this has much to do with Acid2.
No longer blocks: 289480
(In reply to comment #1)
> Perhaps we should put this display check inside of PaintSelf itself.  It'll
> mean calling it more, but I maybe that's OK.

Actually, probably not, since we need it for bug 78087.
Created attachment 181460 [details] [diff] [review]
patch

This is cleaned up a little, but it doesn't actually work.
Attachment #180687 - Attachment is obsolete: true
the code that's patch here will go away in bug 309521
Depends on: 309521
So is this still an issue now that bug 309521 is fixed?  That is, is there a bug when rendering a plug-in in an nsObjectFrame?

Comment 10

13 years ago
This is completely fixed in the latest trunk build of Firefox, possibly because bug 317375 have been fixed.
Status: ASSIGNED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → WORKSFORME

Comment 11

8 years ago
The testcase seems to have regressed badly in Firefox 4.0b8. Should this bug be reopened?

Comment 13

8 years ago
Sorry, not really a regression - I was referring to red visible in the testcase, which is apparently the correct rendering - IE8 and Chrome render the same (though Chrome shows some additional rendering issues).

Updated

5 months ago
Product: Core → Core Graveyard
Component: Layout: Misc Code → Layout
Product: Core Graveyard → Core
You need to log in before you can comment on or make changes to this bug.