Join the AMA (Ask Me Anything) with the Firefox leadership team to celebrate Firefox 20th anniversary and discuss Firefox’s future on Mozilla Connect. Mark your calendar on Thursday, November 14, 18:00 - 20:00 UTC!

Avatar for Username

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

This thread was archived. Please ask a new question if you need help.

When I try to open a YouTube video, the browser repeatedly (and endlessly) opens and closes a couple of tabs.

  • 2 replies
  • 1 has this problem
  • 6 views
  • Last reply by Jason

Jason
Jason
more options

When I try to open a YouTube video, the browser repeatedly (and endlessly) opens and closes a couple of tabs. As you can imagine, the video never displays. Opening the tab in a private window works. I do have the YouTube container installed, so I expect that has something to do with it, but I don't know for certain. In any case, this certainly isn't expected to functionality.

Has anyone seen this before, and know what causes it?

When I try to open a YouTube video, the browser repeatedly (and endlessly) opens and closes a couple of tabs. As you can imagine, the video never displays. Opening the tab in a private window works. I do have the YouTube container installed, so I expect that has something to do with it, but I don't know for certain. In any case, this certainly isn't expected to functionality. Has anyone seen this before, and know what causes it?

All Replies (2)

Jason
Jason Question owner
more options

Disabled the YouTube container, and the problem went away, so it's either something wrong with the container itself, or a bad interaction with another plugin.

Is this a known issue with the container add-on?

Jason
Jason Question owner
more options

Ok, so I was being lazy... I did a little more digging and found out that my presumption was wrong. I had thought this was a plugin from Mozilla, but it turns out to be something another user forked from the Facebook plugin. And it hasn't been maintained in two years. Into the bit-bucket it goes...