Search Issue Tracker
Third Party Issue
Votes
6
Found in
6000.0.54f1
6000.1.14f1
6000.2.0b12
6000.3.0a3
6000.4.0a1
6000.5.0a1
Issue ID
UUM-113452
Regression
No
HTML Drag and Drop API stops working when Cursor.lockState changes on Firefox in a WebGL Standalone Build
How to reproduce:
1. Open the project “IN-109258_DragAndDrop”
2. File → Build and Run
3. Open the localhost link to the built project on Mozilla Firefox
4. Drag and drop any file into the built project
5. Click on the inside of the built project and then click again
6. Press ESC to leave the locked cursor state
7. Drag and drop any file into the built project
9. Observe the Developer Console inside of the build
Expected result: The Developer Console prints out two blob names of the files dragged and dropped
Actual result: The Developer Console prints out only one blob name of the file dragged and dropped before locking the Cursor
Reproducible with: 2022.1.0a1, 6000.0.54f1, 6000.1.14f1, 6000.2.0b12, 6000.3.0a3
Reproducible on: Windows 11
Not reproducible on: No other environments tested
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- URP Realtime reflection probes do not update when RenderProbe() is being called once per second
- Addressable terrain shader variants are stripped from the Player
- [iOS] Debug.Log() appears as <private> in Console app
- UI stays in the background when it is disabled in simulator
- A wrong log file is attached when project is launched with a "-logFile" command line argument
Resolution Note:
Thank you for reporting a bug to Unity.
We have reviewed the issue carefully, and in this case, we determined it is a third-party issue.
We reported the bug to Mozilla: https://bugzilla.mozilla.org/show_bug.cgi?id=1996841.
As a workaround it is possible to use Scripting API to disable the sticky pointer lock mode using "WebGLInput.stickyCursorLock = false;"(https://docs.unity3d.com/ScriptReference/WebGLInput-stickyCursorLock.html) and manually activating the pointer lock mode on click events. This seems to prevent the bug from triggering in most cases.
Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.