Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
2020.2
2020.2.0b5
2021.1
Issue ID
1282698
Regression
No
Selected element cannot be changed visually on package.json Importer dropdown
How to reproduce:
1. Open attached project "PackageScopeBug.zip"
2. In Project Window, select 'Packages' > 'Bug Complex Package Scope' > 'package'
3. In Inspector Window, click right next to Importer to open the Importer dropdown menu
4. Click on UnityEditor.TextScriptImporter(default)
5. Open the same dropdown menu again
Expected result: UnityEditor.TextScriptImporter(default) is the selected element
Actual result: The selected element of the dropdown did not change
Reproducible with - 2020.2.0b7, 2021.1.0a1
Not reproducible with (no feature to choose importer) - 2018.4, 2019.4, 2020.1
Notes:
The importer is actually changed judging from the package.json.meta file
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Objects with Universal Render Pipeline/Particles/Lit shader are always lit up when changing their Rendering Layer Mask
- PolySpatial “Trying to set shader on a Material Variant.” error is printed in the console when entering Play Mode
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
Add comment