Closed Bug 303133 Opened 19 years ago Closed 19 years ago

Regression prevents outer doc accessible from having children

Categories

(Firefox :: Disability Access, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: aaronlev, Assigned: aaronlev)

Details

(Keywords: access)

Attachments

(1 file)

When a frame or iframe is finished loading, we are invalidating the children of
the outer accessible (which represents the frame or iframe element).
Unfortunately, we always create its children on Init() and don't allow
rebuilding of the child information.

Also bad, we always say there is 1 child even if for some reason we can't get
create an inner doc accessible.
Comment on attachment 191441 [details] [diff] [review]
Have inner and outer doc get each other on demand, and remove a couple unnecessary method overrides in nsOuterDocAccessible

In nsDocAccessible, where does mParent get set to a value?
(In reply to comment #2)
> (From update of attachment 191441 [details] [diff] [review] [edit])
> In nsDocAccessible, where does mParent get set to a value?
> 

In ::GetParent()
 +          accService->GetAccessibleFor(ownerNode, getter_AddRefs(mParent));


Attachment #191441 - Flags: review?(parente) → review+
Attachment #191441 - Flags: superreview?(neil.parkwaycc.co.uk) → superreview+
Attachment #191441 - Flags: approval1.8b4?
Comment on attachment 191441 [details] [diff] [review]
Have inner and outer doc get each other on demand, and remove a couple unnecessary method overrides in nsOuterDocAccessible

a=mkaply
Attachment #191441 - Flags: approval1.8b4? → approval1.8b4+
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: