Open Bug 539696 Opened 15 years ago Updated 3 years ago

reorg IEnumVariant implementation

Categories

(Core :: Disability Access APIs, defect)

All
Windows XP
defect

Tracking

()

People

(Reporter: surkov, Unassigned)

References

(Blocks 1 open bug)

Details

(Keywords: access)

Attachments

(1 file)

1) nsAccessible and AccessibleEnumerator implementation are very close and they could share the same implementation especially after we started to use array to store accessible children 2) two ATs can use IEnumVariant the same time and this may make them to get wrong children 3) there is a public copy constructor which should be obviously private (this was inspired by talk with Pete)
Attached patch wipSplinter Review
the main problem I have met is how to unattach the enumvariant when its data are out of date for example when children are changed, accessible goes away, changed the number of selected children. Filing wip, probably once I'll get back.
Depends on: 754879
Alex, still want to do something here? iirc you did a bunch of this stuff a while ago.
(In reply to Trevor Saunders (:tbsaunde) from comment #2) > Alex, still want to do something here? iirc you did a bunch of this stuff a > while ago. per bug description we can say it's fixed, however we still need to clean up AccessibleEnumerator class (perhaps move it to EnumVariant files, address 3d item, keep it updated when array is changed)
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: