Closed Bug 646368 Opened 11 years ago Closed 11 years ago
don't check whether children are cached while tree is traversed
That allows us to not care where GetChildAt/GetChildrenCount() and etc are called from. Otherwise we'd need to make sure we don't call these methods in the middle of update. prevents patch from bug 634218 working.
Assignee: nobody → surkov.alexander
Status: NEW → ASSIGNED
Attachment #523332 - Flags: review?(bolterbugz)
Makes me think we should write down our life cycle assumptions somewhere. I like the patch... I'll review the other one first.
(In reply to comment #2) > Makes me think we should write down our life cycle assumptions somewhere. what is for and what is relation with this bug?
I'm talking about when we expect the a11y tree to be up-to-date. It isn't directly related to this bug.
11 years ago
Attachment #523332 - Flags: review?(bolterbugz) → review+
landed on cedar - http://hg.mozilla.org/projects/cedar/rev/558fff008e74
Status: ASSIGNED → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla2.2
According to hg bisect, this is what is causing bug 705404. The funny this is that removing call to EnsureChildren() is the gist of the patch.
You need to log in before you can comment on or make changes to this bug.