Why does Framer insist on autocorrecting my variables to initial caps on hard return?
Likely your variable is also used inside Framer with different capitalization (screen vs. Screen). Our autocomplete is not smart enough to understand which one you likely mean so you get situations with stupid/annoying predictions. We will address this in the future, but it's a lot of work.
I think I did use a cap initially, but then changed it. I think Framers memory is too good! :)