Closed Bug 625653 Opened 10 years ago Closed 10 years ago

[meta] prevent accessible creation at unsafe time

Categories

(Core :: Disability Access APIs, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED
Tracking Status
blocking2.0 --- final+

People

(Reporter: surkov, Assigned: surkov)

References

Details

(Keywords: access, meta, Whiteboard: [softblocker])

No description provided.
Depends on: 625693
Depends on: 626660
Depends on: 626667
Asking for blocking. This bug consists in that parts of web page content may randomly disappear from screen readers. This bug may be seen on Firefox 3.6 but it appears more often on Firefox 4. I would like all blocking bugs get fixed to guarantee we never encounter the problem on certain web pages.
blocking2.0: --- → ?
What is the scope of this bug? I really don't see how we can block on this now, given that we're trying to get an RC out in 3-4 weeks.
(In reply to comment #2)
> What is the scope of this bug? I really don't see how we can block on this now,
> given that we're trying to get an RC out in 3-4 weeks.

We estimate about 4 weeks to land these fixes but we'd ask for about 5 weeks if at all possible. This estimate includes the huge bus factor on Alexander for this important work.
I'm calling this a softblocker as this package of work includes hard and soft interdependent blockers. We need to have a contingency for how we can release if the entire work package is incomplete when RC comes.
blocking2.0: ? → final+
Whiteboard: [softblocker]
Assignee: nobody → surkov.alexander
IMO it should be hardblocker and desirable betaN blocking. This work may be compared to building basement changing and until we finished it the building may crash eventually. That what we observe from time to time when new landings fix existing problems but new ones appear in unpredictable places.

We were forced to start this work since Gecko 2 is too different and required core accessibility changes, we just weren't in time to finish it.
Depends on: 629862
Depends on: 630001
No longer depends on: 630001
No longer depends on: 626660
No longer depends on: 613058
All dependencies fixed. Nice! Close?
Theoretically there are cases when we may invalidate children and do not update them what may lead to their caching at unsafe time. But I think it can be marked as fixed.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.