We have lot of places where we traverse the tree from bottom to top what's an unoptimal. For example, in HasRelatedContent content where we look whether element is contained by active descendant or in accessible tree update where we look if the accessible is contained by alert or menupopup. In most cases elements aren't contained by accessibles of special types and we traverse the whole document for nothing. We don't have wide spread the accessible adoption (just in few cases) so it shouldn't be perf issue to keep children updated for their parent type. This bug should be really considered as blocking FX 4 release.
How are you imagining this should be implemented? Hashing? Or storing related info/pointers on the accessible children?
(In reply to comment #1) > How are you imagining this should be implemented? Hashing? Or storing related > info/pointers on the accessible children? I have a patch (storing bit flags) but I didn't get a testcase (layout is too smart now) where it shows significant perf win. I just left the bug for now. I'll get back to it soon I think.
OK, be sure to request blocking if/when it makes sense :)
(In reply to comment #3) > OK, be sure to request blocking if/when it makes sense :) right, just pend on it for now and give me a bit more time to do testing.
7 years ago
6 years ago