Search Issue Tracker
Won't Fix
Votes
0
Found in [Package]
0.10.2-preview
Issue ID
1224841
Regression
No
Enum, Tag, Mask, Layer, LayerMask fields result in offset pop-up when clicked and with specific game window size
How to reproduce:
1. Open attached project "War_of_Imbalance_stripped.zip" and scene "ClientMenuScene"
2. Enter Play mode
3. In Game view, choose 16:10 aspect ratio and make the Game view vertically large
4. Click on "Enum Autumn" field
5. Observe the pop-up location
Expected result: the pop-up is near the click position or near the Enum itself
Actual result: the pop-up position is offset
Reproducible with: 2019.3.6f1 (0.10.1-preview), 2020.1.0b2, 2020.2.0a3(0.10.2-preview)
Could not test with: 2017.4, 2018.4 (the UI Builder was not yet implemented)
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
- Texture2D hash changes inside of an AssetBundle when rebuilding a SpriteAtlas bundle with an empty AssetPostprocessor Script enabled
- Aniso Level still applies when Generate MipMap is disabled in Texture Import Settings
- Mipmap Limit Groups long names are not truncated when creating a new Mipmap Limit Group with a long name
- “ArgumentException: Invalid double parameter.” error is thrown when Infinity is typed into the Fixed Timestep field
- GameObject becomes gray when using HDRP and STP together on macOS
Resolution Note:
This bug is a result of a temporary situation, mainly caused by 2 things:
1) All controls listed in this issue are part of the UnityEditor.UIElements namespace. As you probably know (this should be common knowledge at this point) the namespace includes all components that are available from the Editor *only*, i.e. a pure Runtime environment will not grant access to this namespace. In this issue's case, going into Game Playmode while in the editor still allows access to such (editor) controls BUT they will not be available when you build the player (pure Runtime environment).
2) A new feature will be implemented soon on the UIBuilder called "Editor Extensions Mode". This is a preference/setting that, when enabled, allows editor-only controls to be picked from the Editor-only library subsection and added to the UXML document. We have not reached that point yet and so all controls are currently listed in the builder, which might add to the confusion.
With that said, I am closing the bug as won't fix since we have that feature on the way which will at least prevent unauthorized usage of editor-only controls in a runtime environment.