component should also have a getchild method (wishlist)
Bug #257560 reported by
Ara Pulido
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| LDTP |
Fix Released
|
Medium
|
|||
| ldtp (Ubuntu) |
Fix Released
|
Wishlist
|
Unassigned | ||
Bug Description
Binary package hint: ldtp
The way objects are arranged in the AT-SPI layer is very hierarchical.
It makes little sense that only context objects have a getchild method. It
would be very useful if component also had this method.
It will improve a lot the way objects can be recognized. In example, if there
are two text field without name (txt0 and txt1), and one is a child of a tab
page that do have a name, the hierarchy can be used to select the correct text
field.
This can be workaround using getobjectproper
but having getchild method will improve a lot the OO structure of the script
and will allow to search the child by role.
| Changed in ldtp: | |
| importance: | Undecided → Wishlist |
| Changed in ldtp: | |
| status: | Unknown → New |
| Changed in ldtp: | |
| status: | New → In Progress |
| Changed in ldtp: | |
| status: | New → Triaged |
| Changed in ldtp: | |
| status: | In Progress → Fix Released |
Revision history for this message
| Launchpad Janitor (janitor) wrote | #2 |
| Changed in ldtp (Ubuntu): | |
| status: | Triaged → Fix Released |
| Changed in ldtp: | |
| importance: | Unknown → Medium |
To post a comment you must log in.
This was fixed in LDTP 1.6, but it has regressed in LDTP2