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!

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

Cuireadh an snáithe seo sa chartlann. Cuir ceist nua má tá cabhair uait.

YouTube on TV - Device not supported error-Firefox Windows 7/8.1

  • 4 fhreagra
  • 8 leis an bhfadhb seo
  • 2 views
  • Freagra is déanaí ó win7demon

more options

On Windows 7 and 8.1 Chrome and Internet Explorer opens https://www.youtube.com/tv without issue. Using Firefox i get an error stating that YouTube on TV is not supported by this device.

Any ideas?

Thanks

On Windows 7 and 8.1 Chrome and Internet Explorer opens https://www.youtube.com/tv without issue. Using Firefox i get an error stating that YouTube on TV is not supported by this device. Any ideas? Thanks

Athraithe ag win7demon ar

All Replies (4)

more options

I get that, too.

Google's explanation of the error message is: "If you're receiving the message "YouTube on TV is not supported on this device" this means that the device doesn't meet the technical requirements for running the YouTube on TV app."

They don't list desktop or laptop PCs among the compatible devices: http://www.youtube.com/yt/devices/

Not sure how to investigate further. What would be the advantage of accessing this on a desktop/laptop PC?

more options

Its used as a plugin for Windows Media Center.

Not a big issue just means users will have to set it to use an alternate browser that does support it.

more options

This looks like a problem with some Firefox releases. The site works with the current 34 Beta and the current Nightly 36 build, but not in the Firefox 33 release and in the current Aurora 35 build. I don't know what goes wrong as there are no error messages in the browser console and the HTTP request/response headers also do not seem to be given a clue.

more options

Current nightly build 36 is working so definitely a bug.