Open Bug 1327193 Opened 7 years ago Updated 2 years ago

DOM fullscreen notification stays on the screen when I move mouse over devtools

Categories

(Core :: DOM: Events, defect, P5)

Product:
Core
Component:
DOM: Events
Type:
defect

Tracking

()

Tracking Flags:
Tracking Status
firefox50 --- affected
firefox51 --- affected
firefox52 --- affected
firefox53 --- affected

People

(Reporter: arni2033, Unassigned)

References

(Blocks 1 open bug)

Details

>>>   My Info:   Win7_64, Nightly 49, 32bit, ID 20160526082509
STR_1:
1. Open url   data:text/html,<html onclick="this.requestFullscreen()">
2. Open devtools -> inspector
3. Click on the page
4. Keep hovering mouse over different elements in devtools

AR:  Fullscreen notification stays on the screen
ER:  The notification should disappear
The related detection code is in https://dxr.mozilla.org/mozilla-central/rev/cb9f43eb552570e185e95dfc8acb9f9fbe47ae17/browser/base/content/browser-fullScreenAndPointerLock.js#193-224 

It checks the clientY of mousemove event to determine whether to hide the warning. Probably moving in devtools triggers mousemove events with a small clientY?
Blocks: dom-fullscreen-ui
No longer blocks: 1277113
Component: Untriaged → General
Component: General → Untriaged
status-firefox50: --- → affected
status-firefox51: --- → affected
status-firefox52: --- → affected
status-firefox53: --- → affected
Component: Untriaged → DOM: Events
Product: Firefox → Core
I don't seem to have the API enabled on 50.1.0 for whatever reason? This test case also works:

data:text/html,<body onclick="this.mozRequestFullScreen()">test
(In reply to Marcos Caceres [:marcosc] from comment #2)
> I don't seem to have the API enabled on 50.1.0 for whatever reason? This
> test case also works:
> 
> data:text/html,<body onclick="this.mozRequestFullScreen()">test

The unprefixed Fullscreen API is not enabled on release channel and beta channel currently, so you need to use prefixed API there.
Ok, so yeah... it stays up if you hover around for a bit... but it does away if you don't... I think this is pretty minor and probably shouldn't worry about this.
Priority: -- → P5
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.