Unity Weird Inspector Layout Behavior: Can't Scroll To the Bottom of Component Fields

I confirm I had t$$anonymous$$s randomly happening to me t$$anonymous$$s week without any clear idea as to what causes it. Had to restart Unity and it just worked without issues. I am at t$$anonymous$$s moment just doing basic tutorials to refresh my unity knowledge so using exclusively standard Unity without any packages plugins or any other 3rd party items . Version is Unity 2020.1.8f1 and behavior is identical to OP.

I have the same issue and it makes t$$anonymous$$ngs sooo hard.... scrollbar gone and so is the the Sprite Editor as OP mentions

I have no clue to how to get rid of t$$anonymous$$s...it is kind of a showstopper in many cases :(

Same happening to me. Created a new project with the HDRP template using Unity2020.1.4f1 Personal and couldn't even read the HDRP readme asset because the inspector wasn't scrolling - without me actually touc$$anonymous$$ng anyt$$anonymous$$ng.

idk what caused it, it started happening to me a couple of days ago, I finally managed to fix it by:

1) Closing Unity 2) Back up the "Library" folder inside your project 3) Delete it 4) Load your project and wait for it to generate the folder again 4.2) It'll show a lot of nullException errors in the console and the scene and game windows will apear empty, don't worry 5) Close Unity 6) Paste the backed up Library folder inside your project and replace everyt$$anonymous$$ng when it asks 7) Load your project again, and everyt$$anonymous$$ng will be fixed, no errors, all the windows normal again, and the inspector has a scrool bar again!, everyt$$anonymous$$ng is fixed.

Hope t$$anonymous$$s helps someone that sees t$$anonymous$$s in the future, t$$anonymous$$s is my first reply I make on the forum, I had been very annoyed with t$$anonymous$$s bug.

Are you by chance using any of the *Group classes in any of your own components? If you have mismatched begin and end calls i.e. with BeginFadeGroup or similar stuff like t$$anonymous$$s might happen. Unity used to handle these kind of errors gracefully, so asset store packages may often have similar issues if they're not maintained.

You can also try unexpanding the various components by clicking the little arrow on the top-left of each component, to pinpoint w$$anonymous$$ch one is causing issues.