Can someone confirm for me that this example class, which compiles OK but 5289 insists has an unresolved symbol error, behaves the same for them?
The problem appears to a scoping resolution error where the private member focusTraversalPolicy declared in the superclass is disrupting resolution of the subclass variable of the same name.
OK, the code isn't entirely sensible, but it is correct, and didn't produce an IntelliJ error in earlier versions.
A potentially dangerous side-effect is that if you use refactoring to change the variable name at its point of declaration, the usage flagged as an error will not be changed...
Message was edited by: