Bug 493051 - [GTK3] Context menu not fitting to screen shows large white area
Summary: [GTK3] Context menu not fitting to screen shows large white area
Status: RESOLVED WORKSFORME
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 4.6   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Platform-SWT-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: triaged
Depends on:
Blocks:
 
Reported: 2016-05-05 04:16 EDT by Thomas Singer CLA
Modified: 2018-05-08 13:35 EDT (History)
2 users (show)

See Also:


Attachments
screenshot from SmartGit 7.2 preview 5 (38.65 KB, image/png)
2016-05-05 04:16 EDT, Thomas Singer CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Thomas Singer CLA 2016-05-05 04:16:25 EDT
Created attachment 261477 [details]
screenshot from SmartGit 7.2 preview 5

When displaying a larger context menu at a location where it would not fit on the screen, its position is changed correctly, but the content is not.
Comment 1 Eric Williams CLA 2018-05-03 11:17:29 EDT
I believe this has been for awhile now. Thomas can you confirm?
Comment 2 Thomas Singer CLA 2018-05-08 03:02:26 EDT
I can't reproduce this either. But what looks strange to me is that after showing the context menu by right-clicking, I can move the window around or even switch to other applications without the context menu to go away. The only way to dismiss the context menu seems to be to press ESC. Is this expected behaviour on GTK?
Comment 3 Andrey Loskutov CLA 2018-05-08 03:12:36 EDT
(In reply to Thomas Singer from comment #2)
> I can't reproduce this either. But what looks strange to me is that after
> showing the context menu by right-clicking, I can move the window around or
> even switch to other applications without the context menu to go away. The
> only way to dismiss the context menu seems to be to press ESC. Is this
> expected behaviour on GTK?

Which GTK version do you have?
Comment 4 Eric Williams CLA 2018-05-08 09:48:20 EDT
(In reply to Thomas Singer from comment #2)
> I can't reproduce this either. But what looks strange to me is that after
> showing the context menu by right-clicking, I can move the window around or
> even switch to other applications without the context menu to go away. The
> only way to dismiss the context menu seems to be to press ESC. Is this
> expected behaviour on GTK?

It's a known issue on SWT with Wayland. X11 should be fine.
Comment 5 Thomas Singer CLA 2018-05-08 11:55:45 EDT
(In reply to Eric Williams from comment #4)
> (In reply to Thomas Singer from comment #2)
> > I can't reproduce this either. But what looks strange to me is that after
> > showing the context menu by right-clicking, I can move the window around or
> > even switch to other applications without the context menu to go away. The
> > only way to dismiss the context menu seems to be to press ESC. Is this
> > expected behaviour on GTK?
> 
> It's a known issue on SWT with Wayland. X11 should be fine.

I don't know. SmartGit 18.1 should use Wayland by default because of these lines in the startup script:


if [ "$XDG_SESSION_TYPE" = "wayland" ]; then
    export GDK_BACKEND=x11
fi
Comment 6 Eric Williams CLA 2018-05-08 13:35:25 EDT
(In reply to Thomas Singer from comment #5)
> (In reply to Eric Williams from comment #4)
> > (In reply to Thomas Singer from comment #2)
> > > I can't reproduce this either. But what looks strange to me is that after
> > > showing the context menu by right-clicking, I can move the window around or
> > > even switch to other applications without the context menu to go away. The
> > > only way to dismiss the context menu seems to be to press ESC. Is this
> > > expected behaviour on GTK?
> > 
> > It's a known issue on SWT with Wayland. X11 should be fine.
> 
> I don't know. SmartGit 18.1 should use Wayland by default because of these
> lines in the startup script:
> 
> 
> if [ "$XDG_SESSION_TYPE" = "wayland" ]; then
>     export GDK_BACKEND=x11
> fi

I think what you are describing might actually be bug 528998.

As for this ticket, it seems the original problem is gone so I think it's time to close it. Please re-open if you continue to experience the bug.