Etsi tuesta

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Lue lisää

How to grant permanent access to Microphone granted from within an iFrame without being asked for permission everytime?

more options

When I use my Microphone from within an iFrame, I don't have the permanent option. In Chrome it is possible though, and even when loading the Page, which containing the iFrame is loaded twice, the Permission granted for my Microphone is saved permanently. In Firefox, this is different. The Permission granted for the content inside the iFrame is only temporarily, and I don't have the option to give it a permanent Permission. If I launch the content of the iFrame as a standalone website, it is giving me the option to permanently allow this Permission though.

Is there any workaround or can you give me any Hint?

When I use my Microphone from within an iFrame, I don't have the permanent option. In Chrome it is possible though, and even when loading the Page, which containing the iFrame is loaded twice, the Permission granted for my Microphone is saved permanently. In Firefox, this is different. The Permission granted for the content inside the iFrame is only temporarily, and I don't have the option to give it a permanent Permission. If I launch the content of the iFrame as a standalone website, it is giving me the option to permanently allow this Permission though. Is there any workaround or can you give me any Hint?

Valittu ratkaisu

Currently, Firefox cannot store a permanent permission when the host server of the outer page and the framed page are different (for example, Hangouts embedded in Gmail). This might change in a future version but I think it requires the website to send a feature policy header pre-approving it somehow.

Lue tämä vastaus kontekstissaan 👍 1

Kaikki vastaukset (1)

more options

Valittu ratkaisu

Currently, Firefox cannot store a permanent permission when the host server of the outer page and the framed page are different (for example, Hangouts embedded in Gmail). This might change in a future version but I think it requires the website to send a feature policy header pre-approving it somehow.