74628 - Popups, windows do not play the appropriate appearance theme sound

Status: RESOLVED EXPIRED

(SeaMonkey :: UI Design, defect)

Description

[Adam Lock]

Mozilla on the Macintosh does not play appearance theme sounds for events such 
as window scolling, popup menu opening and item selection etc.

Steps to reproduce:

1. Open the Appearance control panel and enable sounds for menus, windows, 
controls etc.
2. Run Mozilla
3. Compare sounds made for popup/bookmark menu opening/closing, tooltips, menu 
item selection, button clicks, scrolling etc. against IE or other applications. 
Mozilla is practically silent.

Mozilla should use the appearance manager to send out the right sounds for these 
user actions.

Comment 1

[Adam Lock]

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

Comment 2

[sairuh (rarely reading bugmail)]

patty/claudius, could one of you take this as qa? thx!

Comment 3

[basic]

Changing platform

Comment 4

[Benjamin Mucci]

Not only the "theme sounds" but all the theme settings: Arrow and Smart
Scrolling. See next attachment.
To reproduce: On any link make: Open link in New Window

Comment 5

[Benjamin Mucci]

Attachment: Left: The parent Window Right: Window open from CM > Open link in New Window

Comment 6

[Paul Chen]

marking p4 and future

Comment 7

[Adam Lock]

CC'ing Chris Saari. This sounds like something Apple would be interested in
seeing fixed sooner than future.

Comment 8

[Asa Dotzler [:asa]]

-> default assignee

Comment 9

[Peter Trudelle]

->future

Comment 10

[Frankie]

Mozilla CFM/Classic build is dead.

Comment 11

[sairuh (rarely reading bugmail)]

actually, i think an OS X system pref exists for sound behavior of UI elements
(under the Sound system pref), so this might be valid for mach-o. reopening.

Comment 12

[Frankie]

Yes, there is a "Play user interface sound effects" checkbox in OSX. However, I
can confirm that Mozilla does indeed play the appropriate sounds: none, just
like all OSX apps.

Comment 13

[Tom Schneider]

Hi - I have no particular interest in this bug but got email
about it.  Yet I am NOT on the CC list and there does
not seem to be any other option to take myself off.
Would someone please explain to me why I got on this bug list
and how to get off again?  Also, how does one get a master
list of all bugs I'm on??

Comment 14

[Frankie]

Tom, you voted for this bug. http://bugzilla.mozilla.org/votes.cgi?action=show_user

Comment 15

[Tom Schneider]

Thanks, that's very weird.  Since I don't use theme sounds,
I would not have voted for it.  Seems unlikely I would have
done so accidently.  Maybe it's a bug in bugzilla that changed my list of votes?
Anyway, I have removed my vote - the only one!

Comment 16

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 17

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 18

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 19

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 20

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 21

[Robert Kaiser]

This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 22

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420