Search Issue Tracker

Fixed

Won't Fix in 6000.3.X, 6000.4.X

Fixed in 6000.5.0a5

Votes

0

Found in

6000.3.0b10

6000.4.0a5

6000.5.0a1

Issue ID

UUM-127025

Regression

No

Clicking on foldout text in the Shader Graph Templates window doesn’t toggle section collapse/expand like clicking the foldout arrow

Visual Effects

-

Steps to reproduce:

  1. Create  a project (Universal 2D)
  2. Go to the "Project" window
  3. Click "Create" -> Shader Graph -> From Template...
  4. Verify that the "Create new Shader Graph Asset" window opens
  5. Click on the category "Basics" and observe the behaviour
  6. Click on the category "Particle" and observe the behaviour
  7. Click on other categories and observe the behaviour

Actual results: Nothing happens

Expected results: Clicking on the foldout text should collapse and expand the section as if the foldout arrow were clicked

Reproducible with versions: 17.5.0(6000.5.0a1), 17.4.0 (6000.4.0a5), 17.3.0(6000.3.0b10)

Not reproducible with versions: -

Can’t test with versions: 17.3.0(6000.3.0a1) as templates feature landed only in 6000.3.0a2

Tested on (OS): macOS - Tahoe 26.1

Notes: Editor Foundations Internal -> Foldout -> Behavior

 

  1. Resolution Note (6000.4.X):

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

  2. Resolution Note (6000.3.X):

    Thank you for reporting a bug to Unity.

    We have reviewed the issue carefully, and in this case, the team is unable to prioritize fixing this bug. There are a number of reasons we make this decision, including the impact and severity of the issue across our user and customer base, and the possibility that future plans may solve the problem in a different way, or that a workaround for the bug may be available.

    Today we will be closing this case. Thank you again for taking the time to report this issue, and please let us know if there is anything else that changes the impact or severity of this issue.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.