Mozilla 도움말 검색

고객 지원 사기를 피하세요. 저희는 여러분께 절대로 전화를 걸거나 문자를 보내거나 개인 정보를 공유하도록 요청하지 않습니다. "악용 사례 신고"옵션을 사용하여 의심스러운 활동을 신고해 주세요.

Learn More

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?

선택된 해결법

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.

문맥에 따라 이 답변을 읽어주세요 👍 1

모든 댓글 (1)

more options

선택된 해결법

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.