Search Issue Tracker
Fixed in 6000.0.44f1
Fixed in 6000.0.X, 6000.1.X, 6000.1.0b12
Votes
0
Found in
6000.0.41f1
6000.1.0b10
Issue ID
UUM-99459
Regression
Yes
Text can be entered into the Console details
How to reproduce:
1. Create a new Unity project
2. Import the attached "uibuildererror" package
3. Make sure warnings have appeared in the Console
4. Select any of the warnings and move to the details
5. Click under the text of the warning
6. Observe the results
Expected results: Text can't be entered
Actual results: The text field becomes active and the text can be enteredÂ
Reproducible with: 6000.1.0b10
Not reproducible with: 6000.0.41f1, 6000.1.0b9
Can't test with: 6000.2.0a6 (Due to another bug)
Reproducible on: macOS Sequoia 15.3 (M1)
Note: The text disappears after deselecting the log
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
- [UWP] Mouse movement re-triggers stale <Mouse>/scroll value after the scroll wheel is used once
- "Shutdown worker was forced killed because it kept running. Worker ..." errors are thrown after building a blank HDRP project
- [UI Toolkit] USS materials in AssetBundles break due to InstanceID referencing a material that no longer exists when a Scene is loaded through Addressables for the second time
- Help button leads to a missing documentation page when clicked on a Font Import Settings in the Inspector
- TextMeshPro Text Component reads bottom-to-top instead of top-to-bottom when using RTL Editor
Resolution Note (fix version 6000.1):
Fixed a bug where it was possible to edit the console content
Resolution Note (fix version 6000.0):
Editor: Fixed a bug where it was possible to edit the console content