Keul Reporter
	Description • 9 years ago

Now that Bug 486262 is fixed, it would be great to have the following enhancement:
- be able to manage sound default activation: always, never, ask
- if set to ask, a tab causing sound should activate a popup or a bar (like a popup tu activate flash) with buttons: always activate by default for this domaine, or activate just now (same action as clicking on the audio tab icon)
- if set to never, no popup is displayed but the sound icon muted is displayed, with the ability to click on it to enable (and maybe a way/tooltip to indicate that sound is disabled by default in preferences)

	Loic
	Comment 1 • 9 years ago

Do you mean an option for the sound activation feature in about:permissions (and ofc in each website's permissions through the favicon)?

	Keul Reporter
	Comment 2 • 9 years ago

Yes, that would be great.
BTW, I just discovered about:permissions why is't there a shodtcut from the firefox option panel?

	(no longer active)
	Comment 3 • 9 years ago

We won't block shipping this feature on this.

	Keul Reporter
	Comment 4 • 9 years ago

Don't know why Loic added in block instead of depends on.
This enhancement can be targeted to milestone 43 or later, but yes, the original (bug 486262) is waited by users and must not be blocked.

	alex_mayorga
	Comment 6 • 9 years ago

Marking NEW as I think Ehsan is on board.

I for one believe having this in about:permissions seems natural.

	Tom Puttemans
	Comment 7 • 9 years ago

I've been looking into this a bit (as perhaps my first contribution) because I'm also interested in it, but I have run into some UX questions about this:

- I don't think having a popup each time a site starts playing audio would be a great default experience for users, wouldn't it make more sense to allow audio by default and have users change from that if they want to? This is the previous browsing experience as well.
- How and when will we visualise that the site has no permission to play audio? Straight away after loading or when it attempts to play some audio? We could re-use the muted tab symbol as that would already be a known feature and use that to allow for temporary unmuting of blocked sites.
- What is the exact interaction with manually muted tabs? What is the behaviour when moving to another site that has permission to play audio in a muted tab? We'll need to distinguish the two types of "mutedness" in some way internally if the behaviour between moving from a blocked site is different from moving from a muted tab.
- Do we need the "Always Ask" option? I'm not convinced that a lot of people would want to receive a popup for each site without preference they visit that starts playing audio.

	Keul Reporter
	Comment 8 • 9 years ago

- In first comment «- if set to ask,» => so it should be enabled by default but can be customised to «ask»
- If no audio is playing, we can see permission with click on icon at left of HTTP>more information>Permission tab, or right click on page>page information>Permission tab. If audio is playing, a muted speaker should appear.
- in permission manager, there's the default option for the website: enabled/ask/deny. If a website is on deny, the click on the speaker should enable sound (and maybe bring a popup: do you want to accept/ask/deny for this website)
- global website preference should be on "accept" by default in about:permissions, and maybe we should document on how there others permissions are implemented.

	Dão Gottwald [:dao]
	Comment 9 • 9 years ago

about:permissions has been removed in bug 933917.