1705504 - window of new profile launches partially hidden behind Windows 8.1 taskbar on the left edge

Status: RESOLVED WORKSFORME

(Core :: Window Management, defect)

Description

[Sebastian Hengst [:aryx] (needinfo me if it's about an intermittent or backout)]

Latest Firefox Nightly 89.0a1 on Windows 8.1, does not reproduce with Windows 10

If the user has the Windows task bar on the left and creates a new Firefox profile, the window gets opened starting from the left of the screen, partially hidden behind the task bar.

Bisection points to bug 1682136 as regressor.

Comment 1

[Masatoshi Kimura [:emk]]

I reproduced this on Windows 10. Moreover, it also reproduced when the Windows task bar is on the top.

Comment 2

[Masatoshi Kimura [:emk]]

Attachment: Bug 1705504 - Set the correct initial window position on the first run. r?Gijs

Since the initial screenX/Y come from hard-coded values in browser.xhtml, they do not care about avail rects.

Comment 3

[Masatoshi Kimura [:emk]]

Could you backout bug 1682136? But please do not close this bug after the backout. This bug should be fixed regardless of the status of bug 1682136.

Comment 4

[Natalia Csoregi [:nataliaCs]]

(In reply to Masatoshi Kimura [:emk] from comment #3)

Could you backout bug 1682136? But please do not close this bug after the backout. This bug should be fixed regardless of the status of bug 1682136.

Backout link: https://hg.mozilla.org/integration/autoland/rev/09908d752facc9c5ec5ddcc2e6fa33895a30070f

Comment 5

[Guilherme Lima]

https://hg.mozilla.org/mozilla-central/rev/09908d752facc9c5ec5ddcc2e6fa33895a30070f - landed yesterday

Comment 6

[Pascal Chevrel:pascalc (PTO until April 26)]

Firefox 89 was fixed by the backout

Comment 7

[Marco Castelluccio [:marco]]

Assuming this is fixed while working on bug 1682136.

Comment 8

[BugBot [:suhaib / :marco/ :calixte]]

The leave-open keyword is there and there is no activity for 6 months.
:enndeakin, maybe it's time to close this bug?

Comment 9

[Emilio Cobos Álvarez (:emilio)]

This was fixed by backout, and the backed out bug is fixed (by another bug). Aryx mentioned the issue is not reintroduced, so I guess we can close this.