1428569 - Windows Taskbar (set to autohide) does not show when the cursor is moved to the bottom of the screen under Remote Desktop

Status: UNCONFIRMED

(Core :: Widget: Win32, defect, P3)

Description

[Dan Gode]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
Build ID: 20180103231032

Steps to reproduce:

I am using Firefox 57.0.4 on Windows Version 10.0.16299 Build 16299. I am connecting to this machine via Microsoft Remote Desktop Beta on Macbook Pro.

I deleted all Firefox data and profiles and installed Firefox 57.0.4 (the most recent version).

No extensions or add ins.

When I open a new Firefox window (not in full screen mode) and move the cursor to the bottom of the screen to switch to another app using the Windows Taskbar, the TaskBar does not pop up (it is set to autohide mode). 

I have to press Command+F11 to toggle full screen mode back and forth to make the Windows Taskbar pop up. This has been happening for several years. This is unique to Firefox. This problem does not arise on Internet Explorer, Edge, or Chrome.

I have tried other browsers 


Actual results:

See above.


Expected results:

See above.

Comment 1

[Erkki Laaneoks]

A some months ago, this problem occurred to the Firefox browser (aurora update channel). If more than 1 window is open, the taskbar auto hide display may work (when moving down with the mouse) and not at the same time on the other window. This may also change during Firefox operation.
Haven't seen any connection with the content of the website.
Thunderbird had the same problem a few months ago. At first Thunderbird starts up, then there is no problem, but during operation, the problem occurs at some unknown time.

This is an annoying problem that interferes with the normal use of Firefox and Thunderbird.

Comment 2

[Ray Kraesig [:rkraesig]]

A some months ago, this problem occurred to the Firefox browser (aurora update channel).

The aurora channel is no longer in use, and hasn't been since before this bug was filed. What Firefox version does Help > About Firefox report?

Also, this user was in an unusual configuration involving Remote Desktop. Is that also the case for you? (If not, it would probably be better to open a new bug.)

Comment 3

[Erkki Laaneoks]

(In reply to Ray Kraesig [:rkraesig] from comment #2)

A some months ago, this problem occurred to the Firefox browser (aurora update channel).

The aurora channel is no longer in use, and hasn't been since before this bug was filed. What Firefox version does Help > About Firefox report?

Also, this user was in an unusual configuration involving Remote Desktop. Is that also the case for you? (If not, it would probably be better to open a new bug.)

I openned Hep => About, and important texts:
"Firefox Developer Edition is up to date
121.0b9 (64-bit)
You are currently on the aurora update channel"

Updates are oftenly.

Comment 4

[Michael Chan]

This bug now exists again in Firefox 133.0

It affects both full screen (F11) and normal maximization of the window. I have to press the Windows key or toggle maximize for the taskbar to be functional again while using Firefox. Does not affect any other application and did not have this problem prior to 133

Comment 5

[Ray Kraesig [:rkraesig]]

Was this seen under Remote Desktop?

• If so, please try using mozregression to narrow down exactly what patch introduced it.

• If not, please file a new bug. This bug is for an obscure issue only affecting users under Remote Desktop... aaaand then also please try using mozregression to narrow down exactly what patch introduced it. (I cannot reproduce the issue under either Win10 or Win11.)

It affects both full screen (F11) and normal maximization of the window.

Not showing the taskbar in fullscreen is intended behavior; Chromium does the same. It should show when maximized, though.

Comment 6

[BugBot [:suhaib / :marco]]

Clear a needinfo that is pending on an inactive user.

Inactive users most likely will not respond; if the missing information is essential and cannot be collected another way, the bug maybe should be closed as INCOMPLETE.

For more information, please visit BugBot documentation.