Closed Bug 31981 Opened 25 years ago Closed 13 years ago

Change EnableRefresh(NS_VMREFRESH_IMMEDIATE) to NS_VMREFRESH_NO_SYNC

Categories

(Core :: Web Painting, defect, P4)

defect

Tracking

()

RESOLVED INCOMPLETE
Future

People

(Reporter: kmcclusk, Unassigned)

References

Details

All of the following places should probably change from passing NS_VMREFRESH_IMMEDIATE to NS_VMREFRESH_NO_SYNC. The NS_VMREFRESH_IMMEDIATE will cause immediate processing of a paint event if the timeout has expired. This is probably not what we want happening in these locations because it will often cause painting when there isn't any content. If they are changed to NS_VMREFRESH_NO_SYNC the painting will occur when the app gets back to the message pump. S:\mozilla\webshell\src\nsWebShell.cpp(3211): vm->EnableRefresh(NS_VMREFRESH_IMMEDIATE); S:\mozilla\layout\base\src\nsDocumentViewer.cpp(506): mViewManager->EnableRefresh(NS_VMREFRESH_IMMEDIATE); S:\mozilla\layout\base\src\nsDocumentViewer.cpp(801): mViewManager->EnableRefresh(NS_VMREFRESH_IMMEDIATE); S:\mozilla\layout\html\document\src\nsHTMLContentSink.cpp(3248): vm->EnableRefresh(NS_VMREFRESH_IMMEDIATE); S:\mozilla\layout\html\document\src\nsImageDocument.cpp(315): vm->EnableRefresh(NS_VMREFRESH_IMMEDIATE); S:\mozilla\layout\xml\document\src\nsXMLContentSink.cpp(1872): vm->EnableRefresh(NS_VMREFRESH_IMMEDIATE);
Hmmmm, I'm not sure why this was given to me. I don't really own most of these callsites. I can change them, but I don't really know what to watch out for in terms of problems etc.
*** Bug 29310 has been marked as a duplicate of this bug. ***
Keywords: donttest
Blocks: 42622
Target Milestone: --- → Future
over to adam lock who's recently been playing w/ painting stuff on the periphery.
Assignee: valeski → adamlock
Search on LXR reveals that NS_VMREFRESH_IMMEDIATE is set in these places /content/base/src/nsDocumentViewer.cpp, line 1006 -- mViewManager->EnableRefresh(NS_VMREFRESH_IMMEDIATE); /content/base/src/nsDocumentViewer.cpp, line 3642 -- mViewManager->EnableRefresh(NS_VMREFRESH_IMMEDIATE); /content/html/document/src/nsImageDocument.cpp, line 421 -- vm->EnableRefresh(NS_VMREFRESH_IMMEDIATE); /content/xml/document/src/nsXMLContentSink.cpp, line 1782 -- vm->EnableRefresh(NS_VMREFRESH_IMMEDIATE); /content/xul/document/src/nsXULDocument.cpp, line 3885 -- vm->EnableRefresh(NS_VMREFRESH_IMMEDIATE);
I am reassigning given the nature of where these calls are occurring. Most appear related to StartLayout or new window operations where the intent is to paint something immediately even when there is no content yet.
Assignee: adamlock → kmcclusk
Component: Layout → Views
Severity: normal → minor
Status: NEW → ASSIGNED
Build moving all existing future-P3 bugs to future-P4.
Priority: P3 → P4
Assignee: kmcclusk → nobody
Status: ASSIGNED → NEW
QA Contact: chrispetersen → layout.view-rendering
EnableRefresh, NS_VMREFRESH_IMMEDIATE, and NS_VMREFRESH_NO_SYNC are all gone now, hooray! So this bug doesn't even make sense anymore.
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → INCOMPLETE
Component: Layout: View Rendering → Layout: Web Painting
You need to log in before you can comment on or make changes to this bug.