Closed Bug 646368 Opened 9 years ago Closed 9 years ago

don't check whether children are cached while tree is traversed

Categories

(Core :: Disability Access APIs, defect)

defect
Not set

Tracking

()

RESOLVED FIXED
mozilla5

People

(Reporter: surkov, Assigned: surkov)

References

(Blocks 1 open bug)

Details

(Keywords: access)

Attachments

(1 file)

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.
Depends on: 646369
Attached patch patchSplinter Review
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.
Attachment #523332 - Flags: review?(bolterbugz) → review+
landed on cedar - http://hg.mozilla.org/projects/cedar/rev/558fff008e74
Whiteboard: [fixed-in-cedar]
http://hg.mozilla.org/mozilla-central/rev/558fff008e74
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Whiteboard: [fixed-in-cedar]
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.
Depends on: 689105
You need to log in before you can comment on or make changes to this bug.