d4f6534e88
Use a Sequence of XAccessible rather than its base interface XInterface for AccessibleRelation's TargetSet. As the targets are accessible objects as well, anything other than XAccessible doesn't make much sense. Using XAccessible right away makes that clearer and avoids the need to query the XAccessible interface. (The winaccessibility bridge was already using `static_cast`, relying on the fact that the objects are XAccessibles.) The a11y UNO API is not published, so an API change should be unproblematic. Change-Id: I7f08e98d1ec303d5343d9a7954187cdd71495ebc Reviewed-on: https://gerrit.libreoffice.org/c/core/+/166586 Reviewed-by: Michael Weghorn <m.weghorn@posteo.de> Tested-by: Jenkins |
||
|---|---|---|
| .. | ||
| qa/cppunit | ||
| signing-keys | ||
| source | ||
| user-template | ||
| CppunitTest_test_a11y.mk | ||
| CppunitTest_test_xpath.mk | ||
| IwyuFilter_test.yaml | ||
| Library_subsequenttest.mk | ||
| Library_test.mk | ||
| Library_test_setupvcl.mk | ||
| Library_vclbootstrapprotector.mk | ||
| Makefile | ||
| Module_test.mk | ||
| Package_unittest.mk | ||
| README.md | ||
| README.vars | ||
Test Harness Code for C++ Unit Testing
Many of these tests are run during the build process. In that case on
unix, if a test fails follow the error messages to debug it under gdb.