Bug 1767448

Summary: Bookmarks toolbar right click of folder doesn't open menu under mouse
Product: [Fedora] Fedora Reporter: Pranav Sharma <pranav.sharma.ama>
Component: firefoxAssignee: Jan Horak <jhorak>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: low Docs Contact:
Priority: unspecified    
Version: 31CC: 0xalen+redhat, anto.trande, gecko-bugs-nobody, jhorak, john.j5live, kengert, pjasicek, rhughes, rstrode, sandmann, stransky
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-11-24 16:48:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 1054334    
Attachments:
Description Flags
about:config
none
screenshot of bug
none
same action but firefox-x11 none

Description Pranav Sharma 2019-10-31 13:37:49 UTC
Description of problem:

In firefox wayland version, when you right click a sub-folder in the
bookmarks toolbar, the menu opens up all the way to the right, instead
of under the mouse.


Version-Release number of selected component (if applicable):

fedora 31 - firefox wayland


How reproducible:

Have bookmarks toolbar with subfolders. Navigate to subfolder
and right click to open menu.


Actual results:

Menu opens up all the way to the right.


Expected results:

Menu opens up under the mouse.


Additional info:

Sorry for the vague info, can provide more details and screenshot when
I come back from work.

Comment 1 Martin Stransky 2019-10-31 13:38:52 UTC
Jan, can you please look at it? Thanks.

Comment 2 Martin Stransky 2019-10-31 13:39:30 UTC
Pranav, can you please attach your about:support? Thanks.

Comment 3 Pranav Sharma 2019-11-01 00:40:28 UTC
Created attachment 1631269 [details]
about:config

Comment 4 Pranav Sharma 2019-11-01 00:41:19 UTC
Created attachment 1631270 [details]
screenshot of bug

Comment 5 Pranav Sharma 2019-11-01 00:41:53 UTC
Hi, I've added a screenshot of the bug and uploaded my about:config.

Comment 6 Pranav Sharma 2019-11-01 00:53:26 UTC
Created attachment 1631274 [details]
same action but firefox-x11

Comment 7 Ben Cotton 2020-11-03 17:13:35 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Ben Cotton 2020-11-24 16:48:11 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.