Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信,及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

Learn More

The expand on Youtube is not working with many Youtube sites and they work on Internet Explorer

  • 2 个回答
  • 54 人有此问题
  • 104 次查看
  • 最后回复者为 gene_wood

more options

On many of the sites on Youtube the expand does not work with Mozilla Firefox 4. I have gone to Internet Explorer and they work there. When I come back from Internet Explorer strange enough the expand on Firefox works. Obviously its picking up programming from Internet Explorer, unfortunately it does not last long. I've tried plug ins, reloading flash player after I deleted it and re-installed it, the problem still exist. Also on the expand screens that do work on the right side there is a very thin white line coming down the border. I'm not the only one with this problem. please help with this problem.

On many of the sites on Youtube the expand does not work with Mozilla Firefox 4. I have gone to Internet Explorer and they work there. When I come back from Internet Explorer strange enough the expand on Firefox works. Obviously its picking up programming from Internet Explorer, unfortunately it does not last long. I've tried plug ins, reloading flash player after I deleted it and re-installed it, the problem still exist. Also on the expand screens that do work on the right side there is a very thin white line coming down the border. I'm not the only one with this problem. please help with this problem.

所有回复 (2)

more options

If you are using the HTTPS Everywhere add-on then disable the rule for Ytimg.com.

Firefox > Add-ons > Options > Search for 'Ytimg' > click the green arrow to change it to a red X.

Close down Firefox.

Open it again and it should work.

Hope this helps :)

more options

Indeed, this is a bug in HTTPS-everywhere which you can see here : https://trac.torproject.org/projects/tor/ticket/4032