Closed Bug 1485955 Opened 6 years ago Closed 6 years ago

No notification to the user if autoplay is configured to permanently allow

Categories

(Firefox :: Site Identity, defect)

63 Branch
defect
Not set
normal

Tracking

()

RESOLVED INVALID
Tracking Status
firefox63 --- affected

People

(Reporter: gpalko, Unassigned)

References

Details

[Environment:] Nightly 63.0a1 BuildId 20180823220048 [Steps:] 1. Open about:preferences#privacy 2. Select "Allow Autoplay" from autoplay dropdown menu 3. Open https://edition.cnn.com/videos in new tab(or any other site which triggers the autoplay doorhanger) 4. Open the Control Center and inspect the Permissions section [Actual Result:] No granted permission is displayed for autoplay with sound [Expected Result:] Automatically Play Media with sound "Allowed" permission should be displayed, since autoplay is configured to permanently allow
Summary: No notification to the user if autoplay is configured to permanently block → No notification to the user if autoplay is configured to permanently allow
Will verify this with UX, but I very much expect that we dont want to do this, the notification when autoplay is blocked helps users in the case that the page might be broken without autoplay and lets them easily enable it, nothing is going to be broken if the user has allowed autoplay, plus is the is audio they will get a tab bar notification Mark should we close this invalid?
Flags: needinfo?(mliang)
I think "Automatically Play Media with sound - Allowed" should only display when the default is block (or always ask) but the website is in the exceptions list with "allowed" status. If the default is allow autoplay then we won't need to display the status in control center even if it's in the exception list. (Because clicking the 'X' in the control center won't do anything in this case.)
Flags: needinfo?(mliang)
Closing this as Invalid, based on the comments above.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.