Community
Participate
Working Groups
build I20060110 - open a CU with some compilation error (in my case it was an unused private field) - place the caret some term that has no error, such as a class name - the highlighting does its thing, and the status line is blank (correct) - place the caret in the range of the error - the highlighting does its thing, and the status line shows the error (correct) - move the caret somewhere else in the range (either using mouse or keyboard) - the highlighting is unchanged (correct) but the status line is cleared (incorrect) It looks like the error display is tied to the highlighting, and is optimized to do nothing when the highlighting is unchanged, but someone else is clearing the status line on every selection. Expectation: the status line shows the error text whenever the caret is within the range of an error (likewise for warnings).
I believe this is a regression, but not sure how recent.
Screen readers have special support for reading the status line. Losing this info is a detriment. The workaround is to use F2.
It's not always failing and sometimes even fails without mark occurrences (see bug 114503).
see also bug 48998.
*** Bug 114503 has been marked as a duplicate of this bug. ***
*** Bug 48998 has been marked as a duplicate of this bug. ***
Fixed in HEAD. Available in builds > N20060410-0010.