Closed
Bug 1015262
Opened 10 years ago
Closed 10 years ago
BasicCompositor does not copy intermediate mShmImage to widget when HAVE_SHMIMAGE on OMTC linux with GTK3
Categories
(Core :: Graphics: Layers, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: fred23, Assigned: fred23)
Details
When Enabling BasicCompositor for OMTC linux GTK3 with layers-use-image-offscreen-surfaces enabled (see bug https://bug1015218.bugzilla.mozilla.org/attachment.cgi?id=8427796) and GTK3 implementation of nsWindow::StartRemoteDrawing() (see https://bug1015211.bugzilla.mozilla.org/attachment.cgi?id=8427786), OnExposeEvent does not get fired perdiodically anymore, but still does on gtk menubar click, for example. So when content changes, the user needs to click on the window to refresh the widget's content.
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → frederic.plourde
Assignee | ||
Updated•10 years ago
|
Summary: nsWindow::OnExposeEvent does not get fired when using BasicCompositor with nsShmImage RenderTarget on OMTC linux with GTK3 → BasicCompositor does not copy intermediate mShmImage to widget when HAVE_SHMIMAGE on OMTC linux with GTK3
the bug this supposedly blocks was resolved. should this be listed as blocking what that bug blocked? bug #994541
Assignee | ||
Comment 2•10 years ago
|
||
(In reply to kxra from comment #1) > the bug this supposedly blocks was resolved. should this be listed as > blocking what that bug blocked? bug #994541 no, the block/depend flags may be removed from both bugs.
Assignee | ||
Comment 3•10 years ago
|
||
This bug no longer applies now that further discussions in bug 1015218 have uncovered some misunderstandings. I'm closing this as INVALID, since the description points to OnExposeEvent while the root cause was in fact related to GetThebesSurface not properly returning an gfxXlibSurface for GTK3 widgets in non-OnExposeEvent cases (like when you Ctrl+ in the browser to scale content) and this has been properly fixed by Bug 1013552.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•