Re: RFR: 8384483: Create implementation of NSAccessibilityTable protocol [v2]

[Alexander Zuev]

On Thu, 6 Aug 2026 18:57:51 GMT, Alexander Zuev <kiz...@openjdk.org> wrote:

>> - To preserve functionality the separate native peers for tables and lists 
>> are created;
>> - The list peer for now reports its role as a table for backward 
>> compatibility, that can be changed later;
>> - Fixed the long existed bug where table reported incorrectly currently 
>> selected rows;
>> - Added accessibilityFocusedUIElement to AccessibleBase;
>> - Added functionality for array attribute count and array attribute values 
>> retrieval to AccessibleBase;
>> 
>> ---------
>> - [x] I confirm that I make this contribution in accordance with the 
>> [OpenJDK Interim AI Policy](https://openjdk.org/legal/ai).
>
> Alexander Zuev has updated the pull request incrementally with one additional 
> commit since the last revision:
> 
>   Fixing the performance on the large tables and lists. In order to do so:
>   - Always return the NSArray of the appropriate size, otherwice VO reports 
> the table size incorrectly;
>   - To avoid querying of the entire content of the control fill in only 
> visible rows +/- additional 10 to avoid incorrect reporting due to the VO 
> caching when navigating with VO controls beyond the visible range;
>   - To request the visible range from the control's skin a new a11y attribute 
> added - VISIBLE_ITEM_RANGE. Since outside of the MacOS it is not used that 
> will not create any problems on other platforms;

> Noted a weird thing (though pre-existing in master): after a cell in the 
> `ListView` is edited, it cannot receive accessibility focus rectangle and the 
> content of it does not announce:
> 
> <img alt="Screenshot 2026-08-11 at 10 13 16" width="403" height="137" 
> src="https://private-user-images.githubusercontent.com/107069028/634385532-1c680e8c-94de-4c19-98d8-4d6141593dd4.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3ODY0Nzk4NjgsIm5iZiI6MTc4NjQ3OTU2OCwicGF0aCI6Ii8xMDcwNjkwMjgvNjM0Mzg1NTMyLTFjNjgwZThjLTk0ZGUtNGMxOS05OGQ4LTRkNjE0MTU5M2RkNC5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjYwODExJTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI2MDgxMVQyMDE5MjhaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT1kZDU3NTBmNWNmYjMxNDg0NWU5NmI1MDhjMzc5MjRkNDgzNzNlOWMwN2VlNGEwYTYzYThhYmE5OGMyZGM0NmY1JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZyZXNwb25zZS1jb250ZW50LXR5cGU9aW1hZ2UlMkZwbmcifQ.wYfcZCLhafswCu6Mx1Ri-NJ9rdjXlvH5DvZEwz-zcZI";>
> also, the tooltip shows `edit to 'update' to commit the change` which is 
> confusing and makes little sense.

Thats... interesting. Seems like another thing i might need to address while 
working on the row a11y peer. Totally unexpected. Where on earth did it get 
data for that that tooltip?

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

PR Comment: https://git.openjdk.org/jfx/pull/2217#issuecomment-5258568198