Closed Bug 1818708 Opened 2 years ago Closed 2 years ago

Download notifications should honor Windows taskbar location

Categories

(Core :: Widget: Win32, defect)

Firefox 111
defect

Tracking

()

RESOLVED INVALID

People

(Reporter: underpass_bugzilla, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:109.0) Gecko/20100101 Firefox/111.0

Steps to reproduce:

With the Windows taskbar located on the top, tried to download a file.

For example,

https://github.com/paintdotnet/release/releases/download/v5.0.2/paint.net.5.0.2.portable.x64.zip

(I have the "Ask always" option for zipfile)

Actual results:

In beta version 111, download notifications are located near in the bottom right corner, thus not honoring taskbar location.

Expected results:

In beta versions before version 111, download notifications were located near in the top right corner. In my opinion, this is the expected behaviour.

Setting the option alerts.useSystemBackend to false, the notification is displayed again in the upper part of the screen.

Thanks for your attention.

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Win32' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Widget: Win32
Product: Firefox → Core

(In reply to Underpass from comment #0)

Actual results:

In beta version 111, download notifications are located near in the bottom right corner, thus not honoring taskbar location.

This is true, and quite surprised me... but it's also a Microsoft decision. As far as I can tell, Windows simply doesn't have any way to allow users or developers to show native Windows notifications anywhere other than the bottom right of the primary monitor.

Sadly, closing as RESOLVED INVALID. You may want to try filing something on Microsoft's Feedback Hub.

(And CCing :nrishel on this, so the relevant team knows about this use case for non-native notifications.)

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.