Closed Bug 391370 Opened 18 years ago Closed 18 years ago

Incomplete state set for ARIA alerts

Categories

(Core :: Disability Access APIs, defect)

x86
Linux
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: scott, Assigned: aaronlev)

References

(Blocks 1 open bug)

Details

The first two buttons on http://www.mozilla.org/access/dhtml/alert bring up ARIA alerts that have incomplete state sets. They only show 'enabled', 'horizontal' and 'showing'. I would expect to see a state set comparable to the state sets seen in the other four examples. It should be noted that these two examples programmatically insert objects into the DOM instead of manipulating style attributes of objects that are already in the DOM.
Scott, what states are missing?
I would also expect to see 'showing', 'visible' and perhaps 'opaque'. Although the first two dialogs are not 'focusable', I would make sure that is not a problem as well.
Notice that bug 390686 only relates to the first 2 buttons. I think this is the same bug.
Depends on: 390686
Scott, this is WORKSFORME in a recent build. Can you try again? It's possible that recent changes fixed it.
What I am seeing is an alert (id=AlertVis) in the ATK hierarchy before an alert has been triggered. That is fine because the states are correct. The states also update properly for this alert when it becomes visible. This may never have been a bug or it may have been fixed by another recent fix. I'm not sure. However, what is clear is that alerts that use different techniques to pop up the alert are exposed differently. I believe the following summarizes how the three different types of alerts are exposed. created in the DOM: new object created visibility style: object always exposed, states updated display style: new object created
It should always be the same, I'll have to look into it.
Scott, I believe your comment 5 is not right. We don't create the visibility alert until it is visible. Tomorrow's build will have some fixes that affect the alert example, could you look again then?
In fact, if it's true, please file a different bug.
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.