ATK GlobalRects giving nonsense locations
Bug #1176234 reported by
Allan LeSage
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
autopilot-gtk |
Incomplete
|
High
|
Alberto Mardegan | ||
autopilot-gtk (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
ken-vandine noticed a failing test based on absurd negative rectangle locations; Ken and I bisected and found that the AddAtkComponent
Ken's failing test is in his branch, lp:~ken-vandine/gnome-control-center-signon/autopilot, name gnome_control_
Related branches
lp:~mardy/autopilot-gtk/lp1176234
- Martin Pitt (community): Approve
- PS Jenkins bot: Approve (continuous-integration)
-
Diff: 11 lines (+1/-0)1 file modifiedlib/GtkNode.cpp (+1/-0)
Changed in autopilot-gtk: | |
status: | Fix Committed → Incomplete |
Changed in autopilot-gtk (Ubuntu): | |
status: | New → Incomplete |
To post a comment you must log in.
One thing I noticed is that all widgets which are not currently visible on screen have a wrong globalRect. What is worse is that I didn't find any way to tell whether a widget is currently visible or not.
I'll try and see if we can at least return a well-known invalid rect in that case (maybe (-1,-1,0,0)) instead of completely random numbers.