RFR: 8283214: [macos] Screen magnifier does not show the magnified text for JcomboBox [v5]

[Alexey Ivanov]

On Thu, 6 Jul 2023 08:32:40 GMT, Abhishek Kumar <abhiscxk at openjdk.org> wrote:

> > But it doesn't look right to me that the drop-down button is the main component of the combo box if it's non-editable. The combo box should handle the accessibility request itself in this case. It still uses the same renderer which can't be put into editable state. The renderer is never added into containment hierarchy.
> 
> In case of non-editable combobox there is no editor as such and arrowButton is the main component. When native side request a11y information, accessible interface for combo button is returned (as only two accessible component are present. One is arrow button and other is popup). Subsequent accessible APIs are invoked for combo button to get accessible name.

Do you think it is correct?

I admit refactoring / rewriting accessibility implementation for `JComboBox` is out of scope in this bug. Yet the current way doesn't feel right.

-------------

PR Review Comment: https://git.openjdk.org/jdk/pull/14497#discussion_r1254252087