1477281 - Autoplay "Allowed Temporary" permission is not displayed in control centre

Status: RESOLVED DUPLICATE of bug 1477273

(Firefox :: Site Identity, defect, P2)

Description

[Gyula Palko[:gpalko]]

[Environment:]
Windows 10, Mac OSX 10.13
Nightly 63.0a1 BuildId 20180720101508

[Steps:]
1. Open https://edition.cnn.com/videos
2. Uncheck the "Remember this decision" checkbox on autoplay doorhanger
3. Click Allow Autoplay

[Actual Result:]
 "Allow Temporary" permission and X button is not displayed in control center  

[Expected Result:]

  "Allow Temporary" permission and X button should be displayed in control center-  Permissions section

[Note:]
 "Block Temporary" status is correctly displayed

Comment 1

[Chris Pearce [:cpearce (Not reading bugmail)]]

While we're showing the doorhanger, the web page is awaiting a response as to whether the user approved the play. So we don't have an X button because it's not clear what response we should send the web page when the X button is clicked. I suppose we if the user closed the prompt by hitting the X button, we could send a "block" response to the web page. Do we show a close button on any other permission prompts?

Comment 2

[Gyula Palko[:gpalko]]

Attachment: allow_temporary.PNG

Comment 3

[Gyula Palko[:gpalko]]

Attachment: blocked_temporary.PNG

Comment 4

[Gyula Palko[:gpalko]]

We don't show a close button on permission prompts. You need to temporary allow autoplay(Step 3) and the permission should be displayed in control center. I've attached screenshots showing the difference between temporary allow and temporary block.

Comment 5

[Chris Pearce [:cpearce (Not reading bugmail)]]

We decided in bug 1477273 comment 12 that we want temporary allow grants to persist for the lifecycle of the tab, so therefore it makes sense for the control center to now show a "temporarily allowed" string here. So we think this should block shipping autoplay v2.

Comment 6

[Dale Harvey (:daleharvey)]

ok cool, will take this and likely close dupe to https://bugzilla.mozilla.org/show_bug.cgi?id=1477273 if it ends up being fixed in a single patch

Comment 7

[Dale Harvey (:daleharvey)]

This is fixed in the other patch