Closed Bug 1460639 Opened 6 years ago Closed 6 years ago

Mozilla Firefox Nightly 62.0a1 (2018-05-10) always starts in windowed/non-maximized mode

Categories

(Firefox :: General, defect)

All
Windows
defect
Not set
major

Tracking

()

VERIFIED FIXED
Firefox 62
Tracking Status
firefox-esr52 --- unaffected
firefox-esr60 --- unaffected
firefox60 --- unaffected
firefox61 --- unaffected
firefox62 - verified

People

(Reporter: mr.rubot, Assigned: bdahl)

References

Details

(Keywords: nightly-community, regression)

Attachments

(2 files)

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:62.0) Gecko/20100101 Firefox/62.0
Build ID: 20180510100205
Summary: Nightly62-may10 will not start up full screen, must click on top right icon → Mozilla Firefox Nightly 62.0a1 (2018-05-10) always starts in windowed/non-maximized mode
Looking on Mozilla Firefox Nightly 62.0a1 (2018-05-10) daily pushlog,
these bugs seems most suspicious:
- Bug 1453788 - Remember window size and location for chrome HTML windows
- Bug 1460116 - Remove ShouldHideScrollbars
- Bug 1457338 - Tap in tab strip stops mouse drags

or it's missed call?
Component: Untriaged → General
Flags: needinfo?(xidorn+moz)
Flags: needinfo?(jhofmann)
Flags: needinfo?(bdahl)
OS: Unspecified → Windows
Hardware: Unspecified → All
Version: unspecified → Trunk
Pretty sure this is from my patch, I'll look into it.
Flags: needinfo?(xidorn+moz)
Flags: needinfo?(jhofmann)
Flags: needinfo?(bdahl)
Assignee: nobody → bdahl
After manually testing the issue I found the following: 

Last good version: Nightly 62.0a1 – Build ID: 20180509100510 – (2018-05-09)
First bad version: Nightly 62.0a1 – Build ID:  20180510100205 – (2018-05-10)
(In reply to Timea Babos from comment #4)
> After manually testing the issue I found the following: 
> 
> Last good version: Nightly 62.0a1 – Build ID: 20180509100510 – (2018-05-09)
> First bad version: Nightly 62.0a1 – Build ID:  20180510100205 – (2018-05-10)

Good, but this is already written in bug summary ;)
Since this has an assignee and we'll see it in regression triage, I don't think we need to specially track it.
I'm also working on a test, but running into intermittent failures do to the way persist values are stored on a timer.
Comment on attachment 8976629 [details]
Bug 1460639 - Apply persisted window settings before layout.

https://reviewboard.mozilla.org/r/244712/#review250844
Attachment #8976629 - Flags: review?(bugs) → review+
this code seems to be very regression prone, so it would be great to get some good tests.
Comment on attachment 8979778 [details]
Bug 1460639 - Add test for loading persisted size of a navigated window.

https://reviewboard.mozilla.org/r/245926/#review252392

::: toolkit/content/tests/chrome/test_navigate_persist.html:42
(Diff revision 1)
> +      win.resizeTo(size, size);
> +      return resizePromise;
> +    }
> +
> +    async function runTest() {
> +      // Test that the persisted window attributes are loaded for browser.xul

I don't understand this comment. I don't see browser.xul being loaded anywhere.
I assume you mean window_navigate_persist.html
Attachment #8979778 - Flags: review?(bugs) → review+
Comment on attachment 8979778 [details]
Bug 1460639 - Add test for loading persisted size of a navigated window.

https://reviewboard.mozilla.org/r/245926/#review252606

::: toolkit/content/tests/chrome/test_navigate_persist.html:42
(Diff revision 1)
> +      win.resizeTo(size, size);
> +      return resizePromise;
> +    }
> +
> +    async function runTest() {
> +      // Test that the persisted window attributes are loaded for browser.xul

I meant for the comment to overall describe what we're trying to test. I've updated it to clarify.
Pushed by bdahl@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/4850c54a299a
Apply persisted window settings before layout. r=smaug
https://hg.mozilla.org/integration/autoland/rev/083bcc5bdad3
Add test for loading persisted size of a navigated window. r=smaug
https://hg.mozilla.org/mozilla-central/rev/4850c54a299a
https://hg.mozilla.org/mozilla-central/rev/083bcc5bdad3
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 62
I'm confirming that bug is fixed, starting in Mozilla Firefox Nightly 62.0a1 (2018-05-25), so I'm marking this bug as VERIFIED. Thank you very much! \o/
Status: RESOLVED → VERIFIED
I have always the problem with last version 62.0a1 (2018-05-24) (64-bit) Xubuntu 18.04 LTS x64
Problem not fixed
(In reply to comment #21)
> I have always the problem with last version 62.0a1 (2018-05-24)

The lastest build is 2018-05-26. If Nightly cannot update itself, download manually here:

http://ftp.mozilla.org/pub/firefox/nightly/latest-mozilla-central/
(In reply to Florent from comment #21)
> I have always the problem with last version 62.0a1 (2018-05-24) (64-bit)
> Xubuntu 18.04 LTS x64
> Problem not fixed

If you would read my comment #20, you will understand properly that this bug:
- is fixed starting in Mozilla Firefox Nightly 62.0a1 (2018-05-25)
- is not fixed in in Mozilla Firefox Nightly 62.0a1 (2018-05-24).
Sorry i thinked my Nightly have been updated.

Repository  http://ppa.launchpad.net/ubuntu-mozilla-daily/ppa/ubuntu is not update with the the last version
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: