Closed
Bug 1478108
Opened 7 years ago
Closed 6 years ago
Slack prompts for autoplay access
Categories
(Core :: Audio/Video: Playback, enhancement, P3)
Core
Audio/Video: Playback
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: ehsan.akhgari, Unassigned)
References
Details
Attachments
(1 file)
49.76 KB,
image/png
|
Details |
See the screenshot.
Getting these prompts for very short audio clips (the kind that Slack plays) is very suboptimal. It would be nice to detect short audio streams, if it is possible, and exempt them from showing these prompts...
Comment 1•7 years ago
|
||
We probably want to allow autoplay on sites that have desktop-notification permissions.
Reporter | ||
Comment 2•7 years ago
|
||
Yes, that would be a good idea, and in my case it would have caused me to not see this permission prompt!
Updated•7 years ago
|
Blocks: delay-autoplay
Updated•7 years ago
|
Rank: 15
Priority: -- → P2
Comment 3•7 years ago
|
||
I'd worry a little bit about putting users in the spot where they can't allow notifications but not autoplay. Social media sites (FB/Twitter) come to mind. But maybe granting notifications could just automatically grant autoplay too. Same net effect, but the user can disable it afterwards?
Also, seems like this is only useful as an optimization for existing sites used by existing Firefox users? At least, I'd assume the autoplay permission prompt would virtually always be encountered before a notification prompt, for a user visiting a new site.
I originally noted the Slack case on, uhh, Slack just because the prompt's wording seems a bit confusing when there's no obvious "media" on the page...
Updated•7 years ago
|
Blocks: block-autoplay
Updated•7 years ago
|
No longer blocks: delay-autoplay
Comment 4•7 years ago
|
||
We talked about this at the block autoplay work week, and decided to not do anything here. It's not obviously good to assume that sites with desktop-notifications should be able to autoplay arbitrary media.
Reporter | ||
Comment 5•7 years ago
|
||
I worry that not addressing this will cause user outrage when this feature hits the release channel... I don't think any user will find our current behavior on these types of websites helpful. :-(
Comment 6•6 years ago
|
||
Since we no longer shipping a prompt I believe this is no longer relevant (the result will now be that the sounds are not audible). Feel free the re-open if you think it's still a problem.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•