Open Bug 1352769 Opened 7 years ago Updated 2 years ago

Focused Firefox windows (and another applications windows) become invisible when notifications from site identity block appear

Categories

(Firefox :: Site Identity, defect, P3)

53 Branch
defect

Tracking

()

Tracking Status
firefox52 --- unaffected
firefox53 - wontfix
firefox54 - fix-optional
firefox55 - affected

People

(Reporter: 684sigma, Unassigned)

References

Details

(Keywords: regression)

User Agent 	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:55.0) Gecko/20100101 Firefox/55.0

I have a problem with Firefox Beta 53. It also happens in Nightly 55. Doesn't happen in Beta 52, ESR 45.
Sometimes when creating / switching to another windows, it stays invisible, if site identity block appears in Firefox window.
Here's a ways to reproduce the bug:

1. Open https://permission.site/ in the last tab, click button "Location" on the page
2. Type anything in location bar
3. Press Ctrl+N (or Alt+Tab to switch to another application)

Result: target window is focused. Old window isn't focused, but it appears ABOVE the new window, making it invisible.
Expected: target window should be visible.

Probably related bugs: Bug 1349453, Bug 1349436.
Has STR: --- → yes
Keywords: regression
I couldn't reproduce this on Mac OS X 10.10 with FF Nightly 55.0a1(2017-04-02).
I did a regression range on Windows 10 x64 and here is the regression window: 

Oh noes, no (more) inbound revisions :(
Last good revision: 771f1590f03efec066b2118cad52f11fd17d43ce
First bad revision: 785314dbec5772bc3b0f0bc18f6ab63fec750193
Pushlog:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=771f1590f03efec066b2118cad52f11fd17d43ce&tochange=785314dbec5772bc3b0f0bc18f6ab63fec750193

 5:11.88 INFO: Looks like the following bug has the  changes which introduced the regression:
https://bugzilla.mozilla.org/show_bug.cgi?id=1328304

Note: I tried to reproduce this on Nightly 53.0a1(2017-01-01) and I couldn't. I also tried with beta 53.0b8(2017-04-03) and the issue is reproducible. From the regression range, it comes out that only version 54 and 55 are affected. 

Johann, do you have any idea why I get this results? If you think the flags are marked in a wrong way, please update them.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Nightly 53 is not affected but Beta 53 is because bug 1328304 landed in Nightly 54 then has been uplift in Aurora 53 (according to the flags).

So versions 53 to 55 are affected.
Flags: needinfo?(paolo.mozmail)
Blocks: 1328304
Flags: needinfo?(paolo.mozmail) → needinfo?(jhofmann)
Too late for a fix for 53. jhofmann, you can let me know if you disagree.
Too late indeed unfortunately, though I really don't like this behavior and it seems like the doorhanger also needs to re-show when clicked the first time.
Flags: needinfo?(jhofmann)
See Also: → 1353976
See Also: → 1353977
See Also: → 1353979
See Also: → 1353980
Windows 7 64 bit, FF 53.0.2 (64-bit)

I may have a similar problem, that has started recently, that I can't seem to fix. When I visit certain websites, that I know track the geolocation, the website will not load. Even when I go into permissions and tell it to allow location, it still doesn't load.
Two examples.
http://www.target.com/
https://www.walgreens.com/offers/offers.jsp?view=weeklyad#/weeklyad

The Target website just has a swirling icon like it is loading the page but never loads anything.
The Walgreens website a pop-up comes on screen. "turn off private browsing mode or update your browser before you continue."

I am not in private browsing mode and seldom even use private browsing.
I have used both of these websites for years without any problems. I recently added the following add-on
https://addons.mozilla.org/en-US/firefox/addon/disconnect/?src=search
This seems to be about the time my trouble started, so I uninstalled this add on but the problem continues.
I wanted to edit to add, that I can no longer see Yahoo emails in Yahoo either.

All of these websites and Yahoo email work fine in Chrome or IE.
Priority: -- → P3
Severity: normal → S3

The severity field for this bug is relatively low, S3. However, the bug has 8 See Also bugs.
:pbz, could you consider increasing the bug severity?

For more information, please visit auto_nag documentation.

Flags: needinfo?(pbz)

The last needinfo from me was triggered in error by recent activity on the bug. I'm clearing the needinfo since this is a very old bug and I don't know if it's still relevant.

Flags: needinfo?(pbz)
You need to log in before you can comment on or make changes to this bug.