Search Issue Tracker
Fixed in 2020.2.X
Fixed in 2019.4.X, 2020.1.X
Votes
1
Found in
2019.3.0a11
2019.3.0f6
2020.1
2020.2
Issue ID
1221561
Regression
Yes
[WebGL] UI Elements appear smaller on builds than in the Editor when the Canvas Scaler is set to Scale with Physical Size
Reproduction steps:
1. Open the attached project ("case_1221561-CanvasScaler.zip")
2. Switch Build Target to WebGL
3. Enter the repro scene ("SampleScene")
4. Make a WebGL build and run it
5. Compare the button inside the build with the button in the Editor
Expected result: Buttons appear to be the same size
Actual result: Button inside the build is significantly smaller
Reproduces on: 2019.3.0a11, 2019.3.4f1, 2020.1.0a26, 2020.2.0a1
Not reproducible with, 2017.4.37f1, 2018.4.18f1. 2019.2.21f1, 2019.3.0a10
Tested on: Chrome (80.0.3987.122), Firefox (73.0.1), using 27 inch Mac (5120 x 2880), but it also reproduces on high-rez Windows monitors
Notes:
1. Other Canvas Scaler options works without issues
2. Also reproduced on Windows machine with monitor resolution 3840x2160
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
- "Shader warning in 'Hidden/Light2D': implicit truncation of vector type" is thrown when building Universal 2D template
- AI Assistant breaks compilation of packages using System.Runtime.CompilerServices.Unsafe via auto-referencing
- Unity Hub checks the "Documentation" module by default on the 6.4 and 6.5 streams despite that it was unchecked with the previous installs
- Shortcut that toggles between Dopesheet and Curves Views in the Animation Window's Timeline is mislabed
- Property List Items Overlap onto the Property List's top edge when scrolling through a long Property List
Resolution Note (fix version 2020.2):
WebGL will provide approximate information about used DPI, based on the assumption that CSS inch is close enough to a physical inch.
Fixed in 2020.2.0a16
Resolution Note (fix version 2020.1):
Fixed in 2020.1.1f1
Resolution Note (fix version 2019.4):
Fixed in 2019.4.9f1