Open Bug 1508272 Opened 6 years ago Updated 2 years ago

When Widevine plug-In is deactivated the video resumes from the minute you started the video initially

Categories

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

defect

Tracking

()

Tracking Status
firefox63 --- affected
firefox64 --- affected
firefox65 --- affected

People

(Reporter: obotisan, Unassigned)

Details

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

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

[Steps to reproduce]:
1. Log into Amazon Prime (https://www.amazon.com/b/ref=lp_2858778011_nav_shopall_aiv?rh=i%3Ainstant-video%2Cn%3A2858778011&ie=UTF8&node=2858778011) and play a video.
2. Let the video play for a few minutes.
3. Go to about:addons -> Plugins.
4. Pay attention at the time the video stop while you deactivate Widevine Content Decryption Module.
5. Activate Widevine again.
6. Refresh the Amazon Prime page and resume the video you were watching. 

[Expected result]:
- The video resumes from the minute you deactivated Widevine (step 4).

[Actual result]:
- The video resumes from the minute you started the video initially (step 1). 

[Regression range]:
- I don't think this is a regression because I can reproduce the issue on Nightly from 2014-01-02. 

[Additional notes]:
- This issue is not related to Widevine. On older versions the issue is reproducing when Silverlight is deactivated.
I'm confused. Does this work as expected without deactivating the CDM ?
Flags: needinfo?(oana.botisan)
It works as expected if the plug-in is activated and the page refreshed. 
The problem is that if you deactivate it, then activate it again, the video starts playing from the time you first started the video, not where it was at the moment the plug-in was deactivated.
Does that clarify things?
Flags: needinfo?(oana.botisan)
The CDM probably stores some state, and we trash that state when deactivating. As such, this is something that would be effected.

Bryce, is this theory plausible?
Flags: needinfo?(bvandyk)
Priority: -- → P3
Indeed, sounds quite plausible.

Thinking out loud: we could try and store information such that when we enable the plugin we would try and seek back to where we left off. I don't know what facility we have for this, if any, currently.
Flags: needinfo?(bvandyk)
Severity: minor → S4
You need to log in before you can comment on or make changes to this bug.