This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
When Description Area obtains focus, then text inside is changed. It seems confusing a bit.
This issue is mostly fixed with my latest commit. There is a bit of an issue: If you have focus on the property sheet, and you shift focus to explorer *while* selecting, the description will not update. The reason for this: For some reason, in NetBeans, when clicking between TopComponents, you do not get *one* FocusEvent that has the previous component in its getOppositeComponent property, and the new component in the getComponent property. Instead, you get two - one FocusEvent saying that focus has shifted from the previous component to null, and then another focus event saying that the focus went to null to the newly focused component. This means my property sheet code cannot tell where focus is going. Rather than write ugly hacks to get around this, I'm hoping it will be solved by the window system rewrite.
FYI, it's now unfixed - in order to make this work, I had to shut off default setting of focus to the table; this breaks opening one editor when another one is open, and makes string editors difficult to open. I think a better solution may simply be to kill the focusability of these components and use JLabels. The descriptions are available as tooltips, which should be accessable, as are the names, so this should not present an accessibility problem.
Still waiting for a response on this issue. My proposal: - Eliminate focusability of text components in the description area - accessibility requirements are satisfied because the same content is available as tooltips in the property sheet & nodes.
I agree, that accessibility stuff is covered enough in Property Sheet & nodes. Then we could eliminate focusability of text components in the DA.
Fixed.