Search Issue Tracker
Won't Fix
Votes
12
Found in
2017.4.0f1
2018.4.0f1
2019.1.0a1
2019.1.0f2
2019.2.0a1
2019.3.0a1
Issue ID
1161544
Regression
No
Mouse position does not match in-game mouse position in WebGL builds when zoom attribute is added to div "unityContainer" block
How to reproduce:
1. Open the attached project ("case_1161544-SimpleDemoProject.zip")
2. Open the repro scene ("SampleScene")
3. Build and run the WebGL build
4. Move the mouse around the scene
5. Confirm that the ray is following the mouse (in-game mouse position matches actual mouse position)
6. Apply "zoom" attribute to "unityContainer" div block
7. Move the mouse around the scene again
Expected results: The in-game mouse position matches actual mouse position
Actual results: The in-game mouse position does not match the actual mouse position
Reproducible with: 2017.4.29f1, 2018.4.2f1, 2019.1.7f1, 2019.2.0b6, 2019.3.0a6
Notes:
1. Tested with Google Chrome (Version 75.0.3770.80 (Official Build) (64-bit)) and Microsoft Edge (Microsoft Edge 42.17134.1.0) browsers
2. Setting the zoom back to the default value (100%) fixes the issue
-
azitennis64
Oct 03, 2020 22:15
Support all data
-
Sliem001
Sep 09, 2020 08:00
need to be fixed in 2020.2 please !
-
unity_wRdLdIzMRzVZOA
Jan 21, 2020 06:55
Needs fixed please. This needs to be fixed.
-
mattone593
Oct 27, 2019 06:04
Isue 2019.2
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
- LineRenderer points lists suffers from performance issues when list is large
- Shaders take a lot of memory at runtime even when only one variant is used
- Lego Microgame crashes the Linux Editor at "ScanFilter::Merge" when selecting a WebGL build location
- GameObject reference is null when creating it inside Reset() function and assigning Script as component
- GameObject/Prefab inspector preview is slow for complex hierarchies
Resolution Note:
This is an edge case scenario that is not likely to affect many users.