1419954 - Xfinity stream videos don't download in Quantum

Status: RESOLVED INCOMPLETE

(Firefox :: Untriaged, defect)

Description

[lchall63]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:57.0) Gecko/20100101 Firefox/57.0
Build ID: 20171112125346

Steps to reproduce:

After updating to Firefox Quantum on my Windows 10 PC, I signed into Xfinity Stream.  Searched for Black Sails series. Loaded the list of available episodes. Picked one to watch. 


Actual results:

Loading screen displayed three rotating dots indicating that the episode is loading but no matter how long I wait the episode doesn't start playing.


Expected results:

The video should have started playing. I verified that the problem was unique to Quantum as it played on my laptop which hadn't yet been updated to Quantum.

Comment 1

[Matthias Versen [:Matti]]

Is it right that you have to be a Comcast customer and have to pay for a "Xfinity Stream" Account if you want to reproduce this report ?

Comment 2

[Cosmin Muntean [:cmuntean], Ecosystem QA]

Unfortunately I can't test this issue since I don't have a Xfinity Stream account. Since you started to encounter this issue only with Firefox Quantum 57, probably this is a regression.

If you don't mind can you please test this issue using a new Firefox profile to eliminate custom settings as a possible cause? Here is a link that can help you: https://goo.gl/f52Jwm

If the issue is still reproducible, probably is a Firefox regression. Can you help as to try to find the regression range? 

Here are the steps how to use mozregression in order to find the regression range and the bug which caused this:
1. First, you will need to download and install Python from ActiveState website: https://www.activestate.com/activepython
2. After installing Python you will need to open a command prompt window and enter the next command "pip install -U mozregression".
3. After doing this you are ready to start digging into builds. You can do that by using the next two commands "mozregression --good <build_date>" (eg: mozregression --good 2014-12-31) when you only know the build when it was ok, or "mozregression --good <build_date> --bad <build_date>" (eg: mozregression --good 2014-12-31 --bad 2015-12-31) when you know both a good build and a bad build.
4. Mozregression will start downloading builds and open them to test your issue. After testing the issue you must validate the build with "good" or "bad". The tool will continue to download and open builds until the search is narrowed down to two builds and will throw a "Pushlog link" that you will need to provide in the bug comment together with any additional information.

Comment 3

[Cosmin Muntean [:cmuntean], Ecosystem QA]

Considering the fact that I don't have a Xfinity Stream account to test this issue and the fact that the reporter did not answered to my request until now, I will mark this as Resolved-Incomplete.

If anyone can still reproduce it on latest versions, feel free to reopen the issue and provide more information.