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 1458034 - Wayland - pop-up is not maximized after maximize request
Summary: Wayland - pop-up is not maximized after maximize request
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 27
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Martin Stransky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks: ffwayland
TreeView+ depends on / blocked
 
Reported: 2017-06-01 19:52 UTC by Martin Stransky
Modified: 2018-11-30 23:23 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-11-30 23:23:01 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Martin Stransky 2017-06-01 19:52:54 UTC 
Description of problem:
https://github.com/stransky/gecko-dev.git package

Maxmize browser window, go to
http://www.autoforum.cz/fascinace/88lety-muz-nechal-25-let-na-zahrade-novy-trabant-a-wartburg-jak-vypadaji-ted/

open any picture in new window. The new window should be maximized but it's not.
Comment 1 Hiroshi Hatake 2017-07-20 08:18:34 UTC 
Is this bug still left?

Maxmizing issue had been fixed at https://github.com/stransky/gecko-dev/commit/36ab77590d39adb2e4775b2e2e10845788b07092 for GNOME on Wayland and weston.

And I hadn't seen this issue in https://github.com/stransky/gecko-dev/commit/2802cca2af95fb68bf276d63fc7322039bc4ba2d.
Comment 2 Martin Stransky 2017-07-31 07:53:51 UTC 
Yes, I still see that. Wayland build from https://firefox-flatpak.mojefedora.cz/ and Fedora 26.

This bug is not about fullscreen but about maximizing pop-up when main window is also maximized.
Comment 3 Hiroshi Hatake 2017-07-31 08:17:09 UTC 
Ah, I got it.
Sorry for my misunderstanding.
Comment 4 Jan Kurik 2017-08-15 09:29:00 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle.
Changing version to '27'.
Comment 5 Ben Cotton 2018-11-27 13:51:49 UTC 
This message is a reminder that Fedora 27 is nearing its end of life.
On 2018-Nov-30  Fedora will stop maintaining and issuing updates for
Fedora 27. 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 '27'.

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 27 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 6 Ben Cotton 2018-11-30 23:23:01 UTC 
Fedora 27 changed to end-of-life (EOL) status on 2018-11-30. Fedora 27 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.
Note You need to log in before you can comment on or make changes to this bug.