When you set the margins to zero on a page with plugins, when Paint is called for the Object Frame, the width of the damage rect is always passed in as zero.
Reassigning to Buster. Peter, if this is blocking rtm++ plugin bugs, please note that.
Assignee: clayton → buster
Currently, we don't optimize the painting region by intersecting with the damage rect because this damage rect isn't always correct. We just paint the whole plugin which causes it to flicker. The intersection is currently #ifdef'ed out and if this bug is something easy to fix, optimization can be turned back on.
per conversation with Peter, marking Future. This is primarily a perf bug. No pages that we know about suffer so much that they are unusable. Peter, 2 things: 1) what platform(s) is this? You have this marked platform=Macintosh with WinNT OS, and last I checked there weren't too many of those out there. 2) could you attach a test case that triggers the problem?
Status: NEW → ASSIGNED
Target Milestone: --- → Future
Reassigning QA Contact for all open and unverified bugs previously under Lorca's care to Gerardo as per phone conversation this morning.
QA Contact: lorca → gerardok
qa contact updated.
QA Contact: gerardok → bsharma
nominating for dogfood (from sdagley's list of bugs that are good candidates for our next release)
SPAM. HTML Element component deprecated, changing component to Layout. See bug 88132 for details.
Component: HTML Element → Layout
buster is gone!
Assignee: buster → peterlubczynski
Status: ASSIGNED → NEW
QA Contact: bsharma → shrir
Peter, is this still an issue?
Ancient bug, no feedback. Closing.
Status: NEW → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.