1353851 - Linux netflix playback is broken in Firefox 55 (Netflix Error Code: F7701-1003)

Status: RESOLVED WORKSFORME

(Core :: Audio/Video: Playback, defect)

Description

[u580221]

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:55.0) Gecko/20100101 Firefox/55.0
Build ID: 20170404100210

Steps to reproduce:

Linux netflix playback is broken entirely in FIrefox 55 (Netflix Error Code: F7701-1003). 
Note: this issue might be related to https://bugzilla.mozilla.org/show_bug.cgi?id=1352934 . However, unlike on what is described there playback for me never works, not even for a few seconds. (It works perfectly in Firefox 54) Therefore, this seems to be something different than just a background suspend issue when the tab becomes inactive.

Steps to reproduce: 1. Login to netflix, 2. Start watching any video


Actual results:

Instant error in FIrefox 55, works fine in FIrefox 54


Expected results:

Works fine in Firefox 55

Comment 1

[u580221]

For what it's worth, I also just tried setting media.suspend-bkgnd-video.enabled to false and it changes nothing - still broken in Firefox 55 on Linux.

Comment 2

[Loic]

Did you test with a fresh profile?
https://support.mozilla.org/t5/Install-and-Update/Use-the-Profile-Manager-to-create-and-remove-Firefox-profiles/ta-p/2914

If it's still broken, could you run the tool mozregression to narrow down a regression range in FF55, please.
See http://mozilla.github.io/mozregression/ for details.
Run the command "mozregression --good=53"(54 is not "registered"), for each build launched, make the test and enter if it's good or bad, then, at the end, paste the final pushlog from mozilla-inbound.

Comment 3

[u580221]

Interestingly, I just upgraded my laptop from 54 to 55 and there it still works. It only broke on my desktop after the 54 -> 55 upgrade.. I'll investigate further.

Comment 4

[u580221]

Ok I dug further and the problem is that with the latest update the setting media.eme.enabled reverted to "false". Firefox 55 also shows this as a default setting on my desktop PC, meaning that if this isn't just that way on my PC anyone who would want to use it would need to dig into about:config first. Is this intentional?

Anyway, changing that setting to "true" makes it work again.