1834982 - visibilitychange event does not trigger on floating window

Status: UNCONFIRMED

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

Description

[[e-mail]]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/113.0.0.0 Safari/537.36 Edg/113.0.1774.50

Steps to reproduce:

Make the browser window floating by hitting restore down.
Open another full screen window on top of this window.

Actual results:

'visibilitychange' event is not sent so the page has no way of knowing it is hidden.

Expected results:

'visibilitychange' event should be sent, so even if the browser is floating we can still stop music + updates etc if the browser is completely hidden.

This is the behavior on other browsers, so I have been sent this issue by our company's QA. Is this a bug or the expected behavior for Firefox?

Comment 1

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

The Bugbug bot thinks this bug should belong to the 'Core::DOM: UI Events & Focus Handling' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 2

[Hsin-Yi Tsai (she/her) [:hsinyi]]

Edgar can help clarify the expected behavior or what the right event is supposed to be used for this case.

Comment 3

[Edgar Chen [:edgar] (Parental leave until Oct. 09.)]

(In reply to [e-mail] from comment #0)

Open another full screen window on top of this window.

Does "another full screen window" refer to another application or another browser window?
I am assuming you mean another application. Can you confirm if my understanding is correct?
Thanks!

Comment 4

[[e-mail]]

Either - another application or another browser window.

Comment 5

[Edgar Chen [:edgar] (Parental leave until Oct. 09.)]

I believe this issue is related to how the widget tracks whether a window is fully occluded by other windows. I do see sometimes visibilitychange isn't triggered even if the window is fully occluded by other windows.

Comment 6

[Ray Kraesig [:rkraesig]]

(Whoops! Bug 1688997 is effectively a meta bug, isn't it. Sorry for the spam.)