720278 - Notifications still appear when in full screen mode.

Status: RESOLVED INVALID

(Firefox :: General, defect)

Description

[Blake Winton (:bwinton) (:☕️)]

Version 11.0a2 (2011-12-22).

I've uninstalled Flash from my MacBook Pro, and I'm trying to play a video in YouTube (http://www.youtube.com/watch?v=dosR50yIyFY&feature=autoplay&list=SP176F977870D23BCA&lf=list_related&playnext=1 to be precise), so I see a notification at the top (http://dl.dropbox.com/u/2301433/Screenshots/Notification.png).

But, when I full-screen the video, the notification is still there (http://dl.dropbox.com/u/2301433/Screenshots/FullScreenNotification.png), which seems wrong, since if I cared about it, I would have dealt with it already, and I just want to watch my video.  :)

Later,
Blake.

Comment 1

[Dão Gottwald [:dao]]

I'm afraid we can't do much about this. If a page claims to require a plugin, we need to tell the user, as the page may not work without it. In this case it does work, but Firefox doesn't really know. Arbitrary content can be made fullscreen, not just videos.

Comment 2

[Blake Winton (:bwinton) (:☕️)]

I'm not sure I'm totally convinced by your explanation.

I agree that we need to tell the user if a plugin is required, but if the user chose to make part of the content fullscreen, whether or not the page works without it, why shouldn't we honour their wishes, and hide the notification?

(Or is the problem that we can't tell whether it was the user or some code on the website asking to go fullscreen, and we don't want to hide the notification if the page just decided to go fullscreen?)

Thanks,
Blake.

Comment 3

[Dão Gottwald [:dao]]

> I agree that we need to tell the user if a plugin is required, but if the
> user chose to make part of the content fullscreen, whether or not the page
> works without it, why shouldn't we honour their wishes, and hide the
> notification?

Because they may have missed it or didn't understand that they may be unable to properly use the page.

Comment 4

[Blake Winton (:bwinton) (:☕️)]

Okay, that's fair enough.  (I would like to hope that people read and understood it, but I realize that's likely not the case. :)

I think that makes this bug invalid (as opposed to wontfix), so I'm marking it as such.

Thanks,
Blake.