Search Support

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.

Learn More

Microphone access in iframe disabled with upgrade to Firefox v107

  • 7 replies
  • 1 has this problem
  • 1 view
  • Last reply by jonzn4SUSE

more options

Hi All,

We recently upgraded to Firefox v107 and started seeing issue where the microphone is not accessible in the iframed page (on windows and mac os). The iframed page has microphone functionality to allow our users to record audio. Both the parent and iframe share the same domain. When i try to enable the microphone nothing happens. I don't see any error messages in console when i click Record button

Any info on what's causing this? It was working on version 106.

Thanks, David

Hi All, We recently upgraded to Firefox v107 and started seeing issue where the microphone is not accessible in the iframed page (on windows and mac os). The iframed page has microphone functionality to allow our users to record audio. Both the parent and iframe share the same domain. When i try to enable the microphone nothing happens. I don't see any error messages in console when i click Record button Any info on what's causing this? It was working on version 106. Thanks, David

All Replies (7)

more options

What site are you trying to use the mic?

more options

Hi Jon,

its our Canvas learning management system. In Canvas, we created a tool that is iframed and allows students to record audio. Canvas and our record audio page both have the .columbia.edu domain.

Thanks, David

more options

To clarify, they're on different servers/different hostnames, though they both have the .columbia.edu domain

more options
more options

hi Cor-el,

i did add both sites to the microphone permissions list, with Allow permission, to no avail.

Also when i open the frame in a new tab so that its no longer iframed, the Record functionality works.

Thanks, David

more options

Since it worked in 106 and now not working in 107, I would open a bug and see what the Devs have to say. Just gather screenshots and anything showing it working in 106 and not in 107 for them to review.

https://bugzilla.mozilla.org/home

more options

In my non-Dev opinion, these google results from your title seem to point in the direction of a Dev issue.

Modified by jonzn4SUSE