Closed Bug 1427310 Opened 7 years ago Closed 6 years ago

Closing firefox with Ctrl+Q does not remember window maximization state on next launch

Categories

(Core :: Window Management, defect)

57 Branch
x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1460639

People

(Reporter: medhefgo, Unassigned)

Details

(Keywords: regression)

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:57.0) Gecko/20100101 Firefox/57.0 Build ID: 20171207194519 Steps to reproduce: Closed firefox with Ctrl+Q while window is maximized. Actual results: Firefox starts in a small window instead of maximized. Expected results: Firefox should have started maximized. Note that closing it using the window title close button will remember the maximization state.
I think I encountered this issue on Mac OSX (and saw it on another device). Refreshing my profile solved it: https://support.mozilla.org/en-US/kb/refresh-firefox-reset-add-ons-and-settings Can you try it? I also noticed that the small window is the default size of Tor browser (and Firefox when 1st launched)
Component: Untriaged → Window Management
OS: Unspecified → All
Product: Firefox → Core
Hardware: Unspecified → All
Status: UNCONFIRMED → NEW
Ever confirmed: true
This is on Linux with a fresh profile. I probably wouldn't have bothered reporting otherwise :P Anyways, turns out this is a relatively old regression, I only just now learned how to reproduce. 6:13.37 INFO: Last good revision: 679118259e91f40d4a8f968f03ec4cff066cdb5b (2016-07-10) 6:13.37 INFO: First bad revision: 214884d507ee369c1cf14edb26527c4f9a97bf48 (2016-07-11) 6:13.37 INFO: Pushlog: https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=679118259e91f40d4a8f968f03ec4cff066cdb5b&tochange=214884d507ee369c1cf14edb26527c4f9a97bf48 Unfortunately, mozregression cannot get me any further cause these commits are too old. I can probably do a manual bisection if needed, but would prefer to avoid it.
Has Regression Range: --- → yes
Keywords: regression
OS: All → Linux
Hardware: All → x86
Finally managed to get a build environment that actually produced some builds. The first bad revision is: changeset: 304400:489a2db1b165 parent: 304399:4ee47bdad6af parent: 304329:679118259e91 user: Phil Ringnalda <philringnalda@gmail.com> date: Sat Jul 09 09:01:35 2016 -0700 summary: Merge m-c to m-i Regression found using mozcommitbuilder 0.4.10 on linux2 at 2017-12-30 14:36:21
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.