Oana Botisan, Desktop QA Reporter
	Description • 6 years ago

[Affected versions]:
- Nightly 65.0a1
- Firefox 64.0b10
- Firefox 63.0.3

[Affected platforms]:
- Windows 10 x64
- Ubuntu 18.04 x64
- macOS 10.14

[Steps to reproduce]:
1. Log into netflix.com
2. From the computer settings change the hour backwards with one hour.
3. Set the hour forwards in order for the clock to show the correct time. 
4. Wait about 10-20 seconds. 

[Expected result]:
I am not sure which is the expected result here. It's either:
- The video is not affected at all (Chrome has this behaviour).

or

- The video stops and an error is displayed on the screen. 

[Actual result]:
- The video pauses.

[Regression range]:
- I am not sure if this is a regression, because I am not sure about the expected result.
- On Nightly from 2014-01-02, the video stops after step 3. 

[Additional notes]:
- I can't reproduce this issue on Chrome.

	Oana Botisan, Desktop QA Reporter
	Comment 1 • 6 years ago

I forgot to mention at step one that you have to play on of the videos. Sorry for the inconvenience.

	Oana Botisan, Desktop QA Reporter
	Comment 2 • 6 years ago

I found out something that I think might be related to this issue. 
If you play a video on Netflix and then put the computer on sleep mode. After an hour when the computer is turned on again, the video pauses after 10-20 seconds.

	Paul Adenot (:padenot)
	Comment 3 • 6 years ago

Is this expected? Are we using the system's clock to do anything here?

	Jean-Yves Avenard [:jya]
	Comment 4 • 6 years ago

While we don't, the CDM likely does and the key could be discarded.

I would expect to see the same behaviour with Chrome though, and it's not

	Alex Chronopoulos [:achronop]
	Comment 5 • 5 years ago

A friendly reminder to :bryce to check and clean this NI (more than 2 weeks old).

	Bryce Seager van Dyk [:bryce] (he/him) - Not reading bugmail
	Comment 6 • 5 years ago

Appreciate the reminder. I'm going to hold the ni for (a little) longer -- I'm hoping to get some time to investigate this in some detail so we can explain the difference between us and Chrome noted in comment #4.