103764 - Anonymous content XUL buttons not recognizing implements=""

Status: RESOLVED INVALID

(Core :: XUL, defect, P1)

Description

[John Gaunt (redfive)]

The ok/cancel/help buttons at the bottom of the preferences dialog do not
recogonize the nsIAccessibleProvider interface as specified in the bindings for
a button:

<binding id="button-base"
extends="chrome://global/content/bindings/general.xml#basetext">
    <implementation implements="nsIDOMXULButtonElement, nsIAccessibleProvider">

The other buttons in the pref-panels are all happy with this and repspond
correctly when QId to an nsCOMPtr<nsIAccessibleProvider>

Comment 1

[David Hyatt]

I am completely baffled by this bug.  I have no idea why this  would be happening.

Comment 2

[John Gaunt (redfive)]

adding jst and jband. hopefully they can lend some direction. :-)

Comment 3

[Aaron Leventhal]

What debugging methods are available here?

Can anyone think of a good place to put printfs/dumps/breakpoints to see what
codepath is being taken/not taken when it should be?

Comment 4

[Aaron Leventhal]

Marking INVALID. This is working just fine.

Accessibility's current problems are actually caused by the following:

1. The accessibility code doesn't walk into anonymous content nodes at all --
that is why we don't see the buttons in <dialog>. It is also why we were no
longer seeing any HTML content -- <tabbrowser> has <browser> as anonymous
content. Looks like we need to walk into anonymous content.

2. Anonymous content nodes have no unique contentID. Can that change? We use
these to have a unique identifier for events, so that a calling process can call
back with the unique ID and find out where the event occured. Unique ID's are
better than generated-on-the-fly ID's for this, because they stay constant, and
can be used by the calling process to check where things are occuring in their
own structures.

Comment 5

[Firefox Bug Husbandry Bot]

https://bugzilla.mozilla.org/show_bug.cgi?id=1527381