After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 708087 - Scrolling leads to bogus accessible extents being reported by the list items
Scrolling leads to bogus accessible extents being reported by the list items
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Accessibility
unspecified
Other Linux
: Normal normal
: ---
Assigned To: gtk-bugs
gtk-bugs
Depends on:
Blocks:
 
 
Reported: 2013-09-14 21:09 UTC by Joanmarie Diggs (IRC: joanie)
Modified: 2018-04-15 00:23 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
listener (393 bytes, text/x-python)
2013-09-14 21:09 UTC, Joanmarie Diggs (IRC: joanie)
  Details
widgetaccessible: Translate widget coords to viewport coords (1.21 KB, patch)
2013-09-26 14:08 UTC, Rui Matos
none Details | Review

Description Joanmarie Diggs (IRC: joanie) 2013-09-14 21:09:04 UTC
Created attachment 254948 [details]
listener

Steps to reproduce:
1. Launch the attached listener in a terminal
2. Get into the Universal Access panel, arrow down to the bottom
3. Arrow back up to the top

Expected results: Each list item printed in the terminal would have the correct extents (bounding box).

Actual results: After scrolling down, the extents reported are something like

    (-2147483648, -2147483648, 625, 44)

And remain this way until the panel has been scrolled back to the top.

Notes:

1. This may be a GtkListBox bug, but the bug doesn't happen with the ListBox demo from gtk3-demo. There the extents are always reasonable.

2. You'll need Gtk+ from master as the listener is looking for an accessible role that has only just recently been properly-exposed.
Comment 1 Rui Matos 2013-09-26 14:08:11 UTC
Created attachment 255837 [details] [review]
widgetaccessible: Translate widget coords to viewport coords

We need to translate widget coords to viewport coords for the
allocations comparison to be meaningful.
--

This seems to fix it, but the whole gtk_widget_accessible_on_screen()
function assumes things which don't really hold. I'm not sure it can
even be made totally correct and not just a best effort.
Comment 2 Matthias Clasen 2018-02-10 05:04:45 UTC
We're moving to gitlab! As part of this move, we are moving bugs to NEEDINFO if they haven't seen activity in more than a year. If this issue is still important to you and still relevant with GTK+ 3.22 or master, please reopen it and we will migrate it to gitlab.
Comment 3 Matthias Clasen 2018-04-15 00:23:35 UTC
As announced a while ago, we are migrating to gitlab, and bugs that haven't seen activity in the last year or so will be not be migrated, but closed out in bugzilla.

If this bug is still relevant to you, you can open a new issue describing the symptoms and how to reproduce it with gtk 3.22.x or master in gitlab:

https://gitlab.gnome.org/GNOME/gtk/issues/new