User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20041018 Firefox/1.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20041018 Firefox/1.0 Firefox does not use the Windows Sounds for Menu Command and Menu Popup (as defined in Control Panel). Also no sound is made when you click a link, the Start Navigation sound (and possibly Stop Navigation) could be used for this purpose. Finally the "Phrase not found" sound is not configurable. It should use the Exclamation sound from Control Panel. Reproducible: Always Steps to Reproduce: N/A If you don't like the sound effects then you can always disable them, but the fact they're not customisable isn't very user friendly.
dupe of bug 248380 ?
Severity: normal → enhancement
Not really - bug 248380 deals only with Start Navigation sounds, this bug deals with all the sounds that should be there. I don't know if this is a bug or an enhancement, all the MS and Non MS apps i've used play the Menu Command and Menu Popup sounds and it's strange using an app that doesn't. Likewise most apps have configurable sounds (such as a failed search sound). Therefore I think the above two are bugs on Windows. The Start Navigation is an enhancement though, which should be left to bug 24380.
Severity: enhancement → normal
Oops I meant bug 248380.
its an enhancement. No one has implemented this, so it would be an enhancement request to add support for this on Windows.
Severity: normal → enhancement
I can see your point but on the other hand the Windows UI has menu sounds as standard (all other apps use it). Therefore Firefox is not providing a standard Windows interface. For example if the Firefox window was non-resizable or modal it would be marked as a bug, even though it technically isn't. Either way it should be fixed/added IMHO.
dupe of Seamonkey bug 83056
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Confirming feature request, seems like a valid idea to me.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Duplicate of this bug: 248380
is there a way to set this wanted‑firefox3.2 now that bug 83056 is fixed ?
This bug report isn't useful because this bug has 3 issues. The menu related sounds were already implemented in bug 83056. The start/end navigation sounds are reported on bug 248380 but that was marked as duplicate of this bug. And the last issue, "Phrase not found" sound is not reported in another bug. So, I suggest that this bug should track the last issue. And bug 248380 should be reopened for the navigation sounds.
Not part of the shell integration code. Moving to widget.
Component: Shell Integration → Widget: Win32
Product: Firefox → Core
QA Contact: shell.integration → win32
I wonder if this should be in accessibility vs. widget.
Summary: Firefox does not use Windows Sounds → Accessibility "phrase not found" sound can't be configured
8 years ago
You need to log in before you can comment on or make changes to this bug.