318988 - Allow user to disable sounds and videos embedded in webpages

Status: RESOLVED DUPLICATE of bug 24418

(Firefox :: Settings UI, defect)

Description

[tyl2]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5

According to W3C accessibility guildline (Checkpoint 3.3 and 3.4 - Allow user to turn on and off rendering of video and audio), this feature should be implemented.

Reproducible: Always

Steps to Reproduce:
Has anyone not been annoyed by some cracking sound a web designer thought was brilliant (but to belabor the point, really is not)?


Expected Results:  
A preference item should be added, just as image loading is already.

Comment 1

[tyl2]

Sorry, forgot to mention that Bug #24418 is the same bug but reported for SeaMonkey only.

Comment 2

[Dave Townsend [:mossop]]

How is this different to bug 313433?

Comment 3

[:Gavin Sharp [email: [e-mail]]]

(In reply to comment #2)
> How is this different to bug 313433?

Presumably because this is about disabling sound or video individually.

(In reply to comment #1)
> Sorry, forgot to mention that Bug #24418 is the same bug but reported for
> SeaMonkey only.

Being able to do something like that would involve a lot of core changes, mostly to the plugin API, so having seperate SM/FF bugs on it isn't really useful. Bug 24418 needs a new component.

Comment 4

[Jo Hermans]

*** Bug 319425 has been marked as a duplicate of this bug. ***

Comment 5

[Ria Klaassen (not reading all bugmail)]

*** Bug 321430 has been marked as a duplicate of this bug. ***

Comment 6

[Dave Townsend [:mossop]]

As per Gavin's suggestion, duping to the core bug.


*** This bug has been marked as a duplicate of 24418 ***

Comment 7

[tyl2]

I won't reopen this bug yet, as I want to hear from others first, but I think AppSuite bugs should be resolved to be duplicates of Firefox bugs, not the other way around. And if Core needs be changed, then maybe it should be assigned to the Core component instead?

Comment 8

[Dave Townsend [:mossop]]

As Gavin said, 24418 needs a new component.