| Summary: | [ATSPI] accessibility/dropdown-value.html is timing out since added in 248145@main | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Lauro Moura <lmoura> | ||||
| Component: | Accessibility | Assignee: | Nobody <webkit-unassigned> | ||||
| Status: | RESOLVED FIXED | ||||||
| Severity: | Normal | CC: | andresg_22, bugs-noreply, cgarcia, webkit-bug-importer | ||||
| Priority: | P2 | Keywords: | InRadar | ||||
| Version: | WebKit Nightly Build | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| See Also: | https://bugs.webkit.org/show_bug.cgi?id=237483 | ||||||
| Attachments: |
|
||||||
|
Description
Lauro Moura
2022-03-11 19:54:00 PST
The problem is that the test expects that select element exposes the selected item text as string value. That's not the case of ATK/ATSPI. We can make it work in all platforms by waiting for the selected index to change instead (selectedChildAtIndex). If the intention of the test is to specifically check the string value, then it's better to move it under mac platform dir. Btw, Andrés, please don't skip tests that aren't platform specific for GTK, because we might not notice it. If a test is failing for GTK just add us to the CC. If you are in a hurry, it's better to land the patch with the test failing for GTK than skipped for GTK. (In reply to Carlos Garcia Campos from comment #2) > The problem is that the test expects that select element exposes the > selected item text as string value. That's not the case of ATK/ATSPI. We can > make it work in all platforms by waiting for the selected index to change > instead (selectedChildAtIndex). If the intention of the test is to > specifically check the string value, then it's better to move it under mac > platform dir. > > Btw, Andrés, please don't skip tests that aren't platform specific for GTK, > because we might not notice it. If a test is failing for GTK just add us to > the CC. If you are in a hurry, it's better to land the patch with the test > failing for GTK than skipped for GTK. Sorry about that, thought you were monitoring the GTK skips. Will do as suggested. (In reply to Andres Gonzalez from comment #3) > (In reply to Carlos Garcia Campos from comment #2) > > The problem is that the test expects that select element exposes the > > selected item text as string value. That's not the case of ATK/ATSPI. We can > > make it work in all platforms by waiting for the selected index to change > > instead (selectedChildAtIndex). If the intention of the test is to > > specifically check the string value, then it's better to move it under mac > > platform dir. > > > > Btw, Andrés, please don't skip tests that aren't platform specific for GTK, > > because we might not notice it. If a test is failing for GTK just add us to > > the CC. If you are in a hurry, it's better to land the patch with the test > > failing for GTK than skipped for GTK. > > Sorry about that, thought you were monitoring the GTK skips. Will do as > suggested. Thanks! So, would it be ok to change the test to wait for selected children change instead? (In reply to Carlos Garcia Campos from comment #5) > So, would it be ok to change the test to wait for selected children change > instead? I think so, as you said we may use selectedChildAtIndex, and perhaps selectedChildrenCount. Can you log the stringValue in GTK for the selection? It would be good to make sure that we don't only have the right selected object but that it also has the right text. (In reply to Andres Gonzalez from comment #6) > (In reply to Carlos Garcia Campos from comment #5) > > So, would it be ok to change the test to wait for selected children change > > instead? > > I think so, as you said we may use selectedChildAtIndex, and perhaps > selectedChildrenCount. Can you log the stringValue in GTK for the selection? > It would be good to make sure that we don't only have the right selected > object but that it also has the right text. Menu items don't expose the value as string value either, but as the name, so I would need to add an exception in WTR. So, maybe the easiest solution after all is to add the exception and leave the test as is. Created attachment 454945 [details]
Patch
Committed r291471 (248587@trunk): <https://commits.webkit.org/248587@trunk> |