Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1673291 - Odd pop-up placement in firefox-wayland
Summary: Odd pop-up placement in firefox-wayland
Keywords:
Status: CLOSED DUPLICATE of bug 1666410
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 29
Hardware: x86_64
OS: Linux
unspecified
unspecified
Target Milestone: ---
Assignee: Martin Stransky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ffwayland
TreeView+ depends on / blocked
 
Reported: 2019-02-07 09:19 UTC by Juan Orti
Modified: 2019-02-28 10:52 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-02-28 10:52:09 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Mozilla Foundation 1339920 0 None None None 2019-02-28 10:51:01 UTC
Mozilla Foundation 1423598 0 None None None 2019-02-28 10:51:01 UTC

Description Juan Orti 2019-02-07 09:19:32 UTC 
Description of problem:
In firefox-wayland, the placement of the pop-ups is very odd. In menus like the browser history, it is drawn partially outside of the screen, making impossible to browse through its sub-menus. Other pop-ups appear far away where they should, for example when clicking in the green lock of a https web site.

I think this issue is worsened when using a multi-monitor setup.

Version-Release number of selected component (if applicable):
firefox-wayland-65.0-2.fc29.x86_64
Comment 1 Christian Stadelmann 2019-02-17 11:06:05 UTC 
This issue is tracked upstream already.
Comment 2 Martin Stransky 2019-02-28 10:52:09 UTC 
It's a duplicate of Bug 1666410.

*** This bug has been marked as a duplicate of bug 1666410 ***
Note You need to log in before you can comment on or make changes to this bug.