https://bugs.documentfoundation.org/show_bug.cgi?id=149952

Michael Weghorn <m.wegh...@posteo.de> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED
                 CC|                            |m.wegh...@posteo.de
             Blocks|                            |36549, 103182
           Assignee|libreoffice-b...@lists.free |m.wegh...@posteo.de
                   |desktop.org                 |

--- Comment #5 from Michael Weghorn <m.wegh...@posteo.de> ---
(In reply to Sebastian Keller from comment #2)
> It is a LibreOffice issue. The gnome-shell magnifier started requesting
> window relative (ATSPI_COORD_TYPE_WINDOW) character extents instead of
> screen relative (ATSPI_COORD_TYPE_SCREEN) ones, because on Wayland
> applications don't really know where their windows are placed on the screen:
> 
> https://gitlab.gnome.org/GNOME/gnome-shell/-/commit/
> cb0c4bd1c2c19645e4cd1be9733c22e8747b07d8
> 
> The coordinates provided by LibreOffice when requesting these window
> relative extents however seem wrong. When looking at the caret coordinates
> in Writer, the coordinates seem to be relative to the paragraph instead of
> the window. So it looks like when ATSPI_COORD_TYPE_WINDOW is requested
> LibreOffice is somehow assuming ATSPI_COORD_TYPE_PARENT.

Thanks, that's extremely helpful!

Indeed, that's exactly what I see when I check the positions with a Writer
paragraph selected in Accerciser:

> In [82]: acc.queryComponent().getPosition(pyatspi.component.XY_SCREEN)
> Out[83]: (1989, 415)
> In [83]: acc.queryComponent().getPosition(pyatspi.component.XY_PARENT)
> Out[84]: (19, 113)
> In [84]: acc.queryComponent().getPosition(pyatspi.component.XY_WINDOW)
> Out[85]: (19, 113)
> In [85]: acc.queryText().getCharacterExtents(0, pyatspi.component.XY_SCREEN)
> Out[86]: (2065, 415, 12, 19)
> In [86]: acc.queryText().getCharacterExtents(0, pyatspi.component.XY_PARENT)
> Out[87]: (76, 0, 12, 19)
> In [87]: acc.queryText().getCharacterExtents(0, pyatspi.component.XY_WINDOW)
> Out[88]: (76, 0, 12, 19)

I'm working on a fix.


Referenced Bugs:

https://bugs.documentfoundation.org/show_bug.cgi?id=36549
[Bug 36549] [META] ACCESSIBILITY: Tracking bug for issues affecting a11y ATK
and GNOME Orca screen reader support
https://bugs.documentfoundation.org/show_bug.cgi?id=103182
[Bug 103182] [META] GTK3-specific bugs
-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to