606547 - container-foo attribute should be available on accessible when hide event is fired

Status: RESOLVED INCOMPLETE

(Core :: Disability Access APIs, defect)

Description

[alexander :surkov (:asurkov)]

That's important for ARIA live region implantation.

Comment 1

[alexander :surkov (:asurkov)]

That stops aria live region removals working. How widely ARIA live regions are spread through the web? Is it ok to deal with this issue at 2.x?

Comment 2

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

I seem to recall that we gave bogus text for removals before so I'm not sure anyone is going to feel pain from this.

My understanding is that .x is supposed to be all about stability and security. It is probably best to target FF5 for this kind of work, which thankfully is going to be date driven (3 months).

I could be wrong on both counts though.

Comment 3

[alexander :surkov (:asurkov)]

(In reply to comment #2)
> I seem to recall that we gave bogus text for removals before so I'm not sure
> anyone is going to feel pain from this.

It should be working for display: node case and be broken for node removals since events were fired async.

> My understanding is that .x is supposed to be all about stability and security.
> It is probably best to target FF5 for this kind of work, which thankfully is
> going to be date driven (3 months).

We should estimate how bad this is it. Perhaps FF5 is right target.

Comment 4

[James Teh [:Jamie]]

FWIW, NVDA doesn't handle live region removal at all. We still haven't seen a use case where this is actually useful to users.

Comment 5

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

(In reply to comment #3)
> (In reply to comment #2)
> > I seem to recall that we gave bogus text for removals before so I'm not sure
> > anyone is going to feel pain from this.
> 
> It should be working for display: node case and be broken for node removals
> since events were fired async.

Ah right. Makes sense.

> 
> > My understanding is that .x is supposed to be all about stability and security.
> > It is probably best to target FF5 for this kind of work, which thankfully is
> > going to be date driven (3 months).
> 
> We should estimate how bad this is it. Perhaps FF5 is right target.

Given comment 4 let's target FF5. Please do renominate for .x if you find a reason.

Comment 6

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

AUTO-CLOSED. This bug untouched for over 2000 days. Please reopen if you can confirm the bug and help it progress.