Open
Bug 24421
Opened 25 years ago
Updated 2 years ago
allow user to slow the presentation rate of audio/video/animations
Categories
(Core :: Disability Access APIs, defect, P5)
Core
Disability Access APIs
Tracking
()
NEW
People
(Reporter: xiaotong, Unassigned)
References
()
Details
(Keywords: access)
This is opened to address priority 1 item according to W3C accessibility guildline. Checkpoint 4.5 - Allow user to slow the presentation rate of audio, video, and animations.
Comment 1•25 years ago
|
||
same as #24413, reassign it to lake to find proper eng. to reassign. We will need to figure out the engineering resource for futuer commitment. UI team can't implement anything.
Assignee: shuang → lake
Moving all UE/UI bugs to new component: User Interface: Design Feedback UE/UI component will be deleted.
Component: UE/UI → User Interface: Design Feedback
Comment 3•24 years ago
|
||
QA Assigning non-confidential New/Assigned User Interface: Design Feedback bugs to Matthew Thomas (mpt@mailandnews.com). Matthew Thomas is now the QA owner for the User Interface: Design Feedback component. (Bugs that involve UI issues in the Netscape-branded Mozilla browser should continue be QA assigned to elig@netscape.com.)
QA Contact: elig → mpt
Comment 4•24 years ago
|
||
Chaning the qa contact on these bugs to me. MPT will be moving to the owner of this component shortly. I would like to thank him for all his hard work as he moves roles in mozilla.org...Yada, Yada, Yada...
QA Contact: mpt → zach
I suppost if the presentation rate could be slowed down, it could be sped up as well.
Comment 7•23 years ago
|
||
Taking, will work with UI team and Pavlov on this one
Assignee: mpt → aaronl
Updated•22 years ago
|
Component: User Interface Design → Browser-General
OS: Windows NT → All
Hardware: PC → All
Updated•20 years ago
|
Priority: P3 → P4
Updated•18 years ago
|
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Comment 8•18 years ago
|
||
Since this bug was written in 2000, I feel this bug probably has been resolved, so I am closing out this bug, if you feel that this has been done in error, please reopen the bug and explain.
Comment 9•18 years ago
|
||
Closing bugs on a whim when you're not the owner of it is NOT the right thing to do. And I'm pretty certain that this bug has not been resolved yet, so I don't know what you're doing.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Updated•18 years ago
|
Status: REOPENED → NEW
Updated•18 years ago
|
QA Contact: zach → accessibility-apis
Comment 10•15 years ago
|
||
Mass un-assigning bugs assigned to Aaron.
Assignee: aaronleventhal → nobody
Comment 11•14 years ago
|
||
Agree speeding up is equally desirable. It might require tinkering with the page's experience of time, e.g. if setTimeout(something,20) should now call back in 10ms. Actually for audio/video triggered purely by setTimeout, it might be possible just to override the setTimeout and Date functions with a userscript.
Updated•7 years ago
|
Priority: P4 → P5
Comment 12•5 years ago
|
||
<video> and <audio> have a play speed context menu. Does that satisfy this request?
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•