<html> <head> <base href="https://bugs.documentfoundation.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - Can't uncheck a toolbar because its menu entry does not fit on screen" href="https://bugs.documentfoundation.org/show_bug.cgi?id=125832#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED DUPLICATE - Can't uncheck a toolbar because its menu entry does not fit on screen" href="https://bugs.documentfoundation.org/show_bug.cgi?id=125832">bug 125832</a> from <a class="email" href="mailto:octallo@alvarezp.org" title="Octavio Alvarez <octallo@alvarezp.org>"> Octavio Alvarez</a> <pre>(In reply to V Stuart Foote from <a href="show_bug.cgi?id=125832#c4">comment #4</a>) > Beleive this is open as <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - Long drop-down menus cover parent toolbar button" href="show_bug.cgi?id=113713">bug 113713</a> NOB against gtk3 composition. > > Workaround of context menu, or of dropping back to the gtk renderer. > > *** This bug has been marked as a duplicate of <a class="bz_bug_link bz_status_RESOLVED bz_closed" title="RESOLVED NOTOURBUG - Long drop-down menus cover parent toolbar button" href="show_bug.cgi?id=113713">bug 113713</a> *** I am not sure it's a duplicate. On one hand, I just tried "SAL_USE_VCLPLUGIN=gtk libreoffice" and it did render the menus differently. Part of those differences is that all toolbars fit within the screen. Also, the menus are scrollable. On the other hand, the topic for the other bug is menu overlapping, effectively being mislocated on the screen, which is definitely not my situation. Also the GTK+ 3 Reference Manual page for GtkMenus mentions menu scrollability [*] so, if the options are there and I don't see any arrows at all it may as well be actually LibO's bug. [*] <a href="https://developer.gnome.org/gtk3/stable/GtkMenu.html#GtkArrowPlacement">https://developer.gnome.org/gtk3/stable/GtkMenu.html#GtkArrowPlacement</a> At the most, I would say that the two bugs are related but daring to call them duplicates is a premature and dismissive resolution. We don't even know if the root cause is the same. IOW, we don't know if fixing 113713 should fix this one too. The most truthful thing to do is to set it back to NEEDINFO and "See also: 113713". I would do it but I don't have the NEEDINFO option. Can someone else do that, please?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>