Show/hide events for progress bars not symmetrical

RESOLVED FIXED

Status

()

Core
Disability Access APIs
RESOLVED FIXED
12 years ago
12 years ago

People

(Reporter: Aaron Leventhal, Assigned: Aaron Leventhal)

Tracking

({access, fixed1.8, sec508})

Trunk
x86
Windows XP
access, fixed1.8, sec508
Points:
---
Bug Flags:
blocking1.8b5 +

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Assignee)

Description

12 years ago
When we fire a show event for a progress bar we also need to fire a hide event
when it goes away.

Otherwise the screen reader starts collecting progress bar objects.
(Assignee)

Comment 1

12 years ago
Created attachment 197045 [details] [diff] [review]
Progress bar was already hidden by the time we were notified
Attachment #197045 - Flags: review?(parente)
(Assignee)

Updated

12 years ago
Flags: blocking1.8b5?
(Assignee)

Updated

12 years ago
Attachment #197045 - Flags: superreview?(neil.parkwaycc.co.uk)

Comment 2

12 years ago
Comment on attachment 197045 [details] [diff] [review]
Progress bar was already hidden by the time we were notified

r+ as long as the change works for popup menus closing also (i.e. the earlier
part of the if construct)
Attachment #197045 - Flags: review?(parente) → review+

Updated

12 years ago
Attachment #197045 - Flags: superreview?(neil.parkwaycc.co.uk) → superreview+
(Assignee)

Updated

12 years ago
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → FIXED
(Assignee)

Updated

12 years ago
Attachment #197045 - Flags: approval1.8b5?

Comment 3

12 years ago
Comment on attachment 197045 [details] [diff] [review]
Progress bar was already hidden by the time we were notified

Approved per 9/26 bug triage meeting.
Attachment #197045 - Flags: approval1.8b5? → approval1.8b5+

Updated

12 years ago
Flags: blocking1.8b5? → blocking1.8b5+

Comment 4

12 years ago
Aaron, time is running out. Better get this landed before we start re-evaluating
our not landed plussed bugs.
(Assignee)

Comment 5

12 years ago
I had forgotten to mark this fixed1.8.
Keywords: fixed1.8
You need to log in before you can comment on or make changes to this bug.