본 사이트는 여러분의 사용자 경험을 개선하기 위해 유지 보수를 진행하는 동안 기능이 제한됩니다. 도움말로 문제가 해결되지 않고 질문을 하고 싶다면 Twitter의 @FirefoxSupport 및 Reddit의 /r/firefox 채널을 활용하세요.

Mozilla 도움말 검색

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

자세히 살펴보기

Autoplay Setting can't make exceptions

  • 5 답장
  • 1 이 문제를 만남
  • 1 보기
  • 최종 답변자: Janell

more options

I usually have it set to block audio and video automatically, and when I'm watching actual videos on Youtube, yeah, I want autoplay turned off. BUT when I'm trying to just play some music, I'd like to allow it. However it's FOREVER TOGGLED OFF EVEN WHEN I SET IT TO ALLOW ALL AUDIO AND VIDEO. It will stay on for one song, and then turn it off again. I also can't allow an exception to that SPECIFIC website because it NEVER shows the blocking autoplay settings in the site info bar, and I can't manually add websites to the exceptions list. So I can't add youtube to my exceptions list, can't change the settings for the page, and even if I do it's NOT paying attention to my choice, even when set to allow for ALL websites.

I usually have it set to block audio and video automatically, and when I'm watching actual videos on Youtube, yeah, I want autoplay turned off. BUT when I'm trying to just play some music, I'd like to allow it. However it's FOREVER TOGGLED OFF EVEN WHEN I SET IT TO ALLOW ALL AUDIO AND VIDEO. It will stay on for one song, and then turn it off again. I also can't allow an exception to that SPECIFIC website because it NEVER shows the blocking autoplay settings in the site info bar, and I can't manually add websites to the exceptions list. So I can't add youtube to my exceptions list, can't change the settings for the page, and even if I do it's NOT paying attention to my choice, even when set to allow for ALL websites.

선택된 해결법

You aren't using Private Browsing mode ?

----

Start Firefox in Safe Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration is causing the problem.

  • switch to the DEFAULT theme: "3-bar" menu button or Tools -> Add-ons -> Themes
  • do NOT click the "Refresh Firefox" button on the Safe Mode start window
문맥에 따라 이 답변을 읽어주세요 👍 1

모든 댓글 (5)

more options

On some websites, the Autoplay permission doesn't display directly in the site information bar. Firefox sometimes only displays this permission if it detects a video trying to autoplay.

However, you can always change that setting by pressing the right arrow in the site information and pressing the More Information button at the bottom of the popup. That opens the Page Info screen. From there, you can select the Permissions tab and find the Autoplay permission listed there. Uncheck the Use Default checkbox and select the option that you want to use for YouTube.

That will also add YouTube to the exceptions list in the regular Firefox settings page.

Hope this helps.

more options

Hi! That worked for adding the allow audio and video specifically to the page (for others you press the right hand arrow next to connections and then the More Information panel is at the bottom, make sure the setting you choose is different from the main one, or it will remove the website from the exceptions list again).

However, the autoplay is still not functioning. It still turns back to off after it autoplays one video, continuous autoplay isn't working.

more options

선택된 해결법

You aren't using Private Browsing mode ?

----

Start Firefox in Safe Mode to check if one of the extensions ("3-bar" menu button or Tools -> Add-ons -> Extensions) or if hardware acceleration is causing the problem.

  • switch to the DEFAULT theme: "3-bar" menu button or Tools -> Add-ons -> Themes
  • do NOT click the "Refresh Firefox" button on the Safe Mode start window
more options

Hi! I wasn't in private browsing mode, but starting it in in safe mode DID get autoplay to work again. I'm going to disable them all and slowly add my apps back in one at a time and see which one is the culprit.

more options

Dug through things for a while, but I couldn't figure out which one caused it because it's working now! I cleaned up some older extensions just in case.