https://bugs.documentfoundation.org/show_bug.cgi?id=153131
--- Comment #60 from Mike Kaganski <[email protected]> --- (In reply to Michael Weghorn from comment #58) > At first glance, it looks like Windows Speech Recognition tries to iterate > over all of the cells of the table (or maybe "just" over the first > 2147483648 ones, since that's the max amount that the 32-bit API allows to > return in `CMAccessible::get_accChildCount`, or whatever other limit Windows > Speech Recognition or some library underneath have). > > ... > > I can't see anything obviously wrong on LO side here, it seems to be getting > requests via the accessibility API that it is handling correctly. I /suspect/ that the API [1] assumes (or allows) the get_accChildCount to return a number only reflecting *visible* children. In this case, scrolling would generate EVENT_OBJECT_CREATE and EVENT_OBJECT_DESTROY events. If you create a test program for texting what Excel reports - the number of accessible children, and maybe which are those - I could test locally for you, and report back, to confirm / reject this suspicion. [1] https://learn.microsoft.com/en-us/windows/win32/api/oleacc/nf-oleacc-iaccessible-get_accchildcount -- You are receiving this mail because: You are the assignee for the bug.
