397800 - Incorrect accParent (Eg: document returns window as parent instead of 'browser'

Status: VERIFIED WORKSFORME

(Core :: Disability Access APIs, defect, P2)

Description

[Kavitha Teegala]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a9pre) Gecko/2007092504 Minefield/3.0a9pre

While navigating the MSAA and IA2 children in the URL("http://www.mozilla.org/projects/minefield/"), it appears as though some of the children are returning incorrect parents. Here are the top-down and bottom-paths generated for the link 'Skip to main content' on the above URL. The key is to note that the parent of the 'document' in the bottom-up view is a window whereas it is 'browser,http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul' in the top-down view. This is verified by UNO Inspect.

View from top-down (i.e. getAccessibleChildren):
/window[@accessibleName='Desktop']
  /clientArea[@accessibleName='Desktop']
    /window[@accessibleName='Minefield Start Page - Minefield']
      /frame[@accessibleName='Minefield Start Page - Minefield']
        /grouping[1]
          /propertyPage[1]
            /browser, http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul[@accessibleName='Minefield Start Page']
              /document[@accessibleName='Minefield Start Page']
                /section[1]
                  /textFrame[1]
                    /link[@accessibleName='Skip to main content']
                  
                  
View from bottom-up (i.e. via getAccessibleParent)
/window[@accessibleName='Desktop']
  /clientArea[@accessibleName='Desktop']
    /window[@accessibleName='Minefield Start Page - Minefield']
      /frame[@accessibleName='Minefield Start Page - Minefield']
        /window[@accessibleName='Minefield Start Page']
          /document[@accessibleName='Minefield Start Page']
            /section[1]
              /textFrame[1]
                /link[@accessibleName='Skip to main content'] 

Reproducible: Always

Steps to Reproduce:
1. Navigate down to the 'browser' field on http://www.mozilla.org/projects/minefield/ (can also be reproduced on any URL).
2. Choose the only child 'document' and get the AccessibleParent for it
3. The parent of document is returned as 'Window' instead of 'browser'
Actual Results:  
The parent of 'document' is returned as 'Window' instead of 'browser'

Expected Results:  
The parent of document should be 'browser'

There are other children which return incorrect parents. Examples are:
1) 'list' is a child of 'frame' and returns an Msaa parent ( Window). All other children of frame seem to return the parent as 'frame'

2) 'propertyPage', child of 'grouping': This should return an IA2 parent 'grouping', however it returns an Msaa parent ( Window).

Comment 1

[Aaron Leventhal]

Here is a test page that has a broken parent chain:
http://dojotoolkit.org/~becky/work/dijit/tests/layout/test_TabContainer.html

The structure contains this:
propertypage
  \ 
   grouping

However, the parent of the grouping is being reported as the window.

Comment 2

[Marco Zehe (:MarcoZ)]

Requesting blocking since this, along with bug 419770, may be a ver yconfusing issue for several screen readers.

Comment 3

[Aaron Leventhal]

Hmm, it appears that the parent of the grouping is a window, because the grouping has a CSS overflow rule and thus has its own window. If we don't provide the window accessible as the accParent there we break AccessibleObjectFromWindow.

We might need to fix the first child of the property page to point to the window, rather than break the way this works.

Comment 4

[Aaron Leventhal]

As it turns out this is similar to bug 419770 but is harder because it's not always an nsDocAccessible and the reporter really wants accParent fixed, not a node_child_of relation.

Comment 5

[Aaron Leventhal]

I have the NODE_CHILD_OF workaround in bug 419770, with try server builds.

Comment 6

[Mike Beltzner [:beltzner, not reading bugmail]]

May be isn't enough to block at this point, please renominate if you meant that it WILL be a confusing issue.

Comment 7

[David Bolter [:davidb] (NeedInfo me for attention)]

Mass un-assigning bugs assigned to Aaron.

Comment 8

[alexander :surkov (:asurkov)]

Marco, is it valid still?

Comment 9

[Marco Zehe (:MarcoZ)]

No, I haven't seen any window hierarchy problems on the Minefield start page in ages. Closing as WFM in Mozilla/5.0 (Windows NT 6.1; WOW64; rv:2.0) Gecko/20100101 Firefox/4.0. Reporter, if you still see a problem, please retest with Firefox 4.0 and reopen if needed.