246501 2022-10-13 20:24:08 -0700 [GTK][a11y] /WebKitGTK/TestWebKitAccessibility:/webkit/WebKitAccessibility/accessible/children-changed is failing 2023-12-01 08:01:24 -0800 1 1 1 Unclassified WebKit Accessibility WebKit Nightly Build Unspecified Unspecified RESOLVED FIXED InRadar P2 Normal --- 1 lmoura webkit-unassigned andresg_22 bugs-noreply cgarcia webkit-bug-importer oldest_to_newest 1905519 0 lmoura 2022-10-13 20:24:08 -0700 /WebKitGTK/TestWebKitAccessibility /webkit/WebKitAccessibility/accessible/children-changed This exact failure is not always happening due to the SDK issue from bug246471, so I had to completely ignore fatal warnings to get to these. EWS history shows this has been failing in a while (couldn't pick up where yet). Notes from investigation: * The test creates a `div` with two `p` - `foo` and `bar` - which are the accessible objects. Working fine. * Then the test creates a new `p`, called `baz`, working fine. * Then the test removes `foo`, working fine. * Then the test changes the role - through JS - of `bar` and checks whether the existing object had its role changed without detach+attach * This test fails, with the existing object still having the role `paragraph` * If I get the children at the same position again, it already has the right `button` role * Also, in line: https://github.com/webkit/webkit/blob/main/Tools/TestWebKitAPI/Tests/WebKitGtk/TestWebKitAccessibility.cpp#L388 * if we replace the `test->stopEventTimer(0, 0.5_s)` with an actual timer, two events are fired: * `object:children-changed:remove` with `detail1 == 1` * `object:children-changed:add` with `detail1 == 0` 1905520 1 webkit-bug-importer 2022-10-13 20:24:19 -0700 <rdar://problem/101156751> 1996187 2 vitaly 2023-12-01 04:27:06 -0800 Pull request: https://github.com/WebKit/WebKit/pull/21155 1996220 3 ews-feeder 2023-12-01 08:01:20 -0800 Committed 271382@main (e32c6f904bc6): <https://commits.webkit.org/271382@main> Reviewed commits have been landed. Closing PR #21155 and removing active labels.