Losing focus in fullscreen mode with UnityWebplayer (not in IE 11 !)

RESOLVED INCOMPLETE

Status

()

defect
RESOLVED INCOMPLETE
4 years ago
3 years ago

People

(Reporter: sputnikbar, Unassigned, NeedInfo)

Tracking

(Blocks 1 bug, {regression})

42 Branch
x86_64
Windows 10
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

()

Reporter

Description

4 years ago
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:42.0) Gecko/20100101 Firefox/42.0
Build ID: 20151029151421

Steps to reproduce:

I'm working on a architecture project with Unity3D 5.0.2. Webplayer deploiement. OS : Win10.
Everything has always been fine with Firefox (thank you !) until the new firefox update :
- check the demo on http://www.dyapo.fr
- toggle fullscreen



Actual results:

move the cursor near the border of the screen you'll see it will go back to the default windows cursor, so clicking in the border of the screen acts like you were clicking on the desktop. So, I lose my fullscreen on the webplayer...
Reporter

Updated

4 years ago
OS: Unspecified → Windows 10
Hardware: Unspecified → x86_64
Component: JavaScript Engine → DOM
Blocks: gecko-games
Xidorn, is this something you could look at? Thanks.
Flags: needinfo?(quanxunzhen)
Keywords: regression
I cannot reproduce this issue locally (with Windows 10 and Firefox 42).

Despite that, it seems to me the Unity Web Player does not do fullscreen via the Fullscreen API, and the Firefox window does not enter fullscreen itself (which is observable if you have multiple monitor and you move the browser window to a secondary monitor before toggling fullscreen), so I don't think we have anything to do on the DOM side.

If this is really a regression of Firefox, it could be some change in the plugin part.
Component: DOM → Plug-ins
Flags: needinfo?(quanxunzhen)
I also cannot reproduce, @Reporter are there more detailed steps that you can provide?
Flags: needinfo?(sputnikbar)
Closing this as incomplete due to inactivity and lack of response from the reporter & WFM info
Feel free to reopen the bug if the issue still reproduces on a current build.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.