Closed Bug 1530378 Opened 5 years ago Closed 5 years ago

CNN native playback no longer works on Win 7

Categories

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

Desktop
Windows 7
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox65 --- affected
firefox66 --- affected
firefox67 --- affected

People

(Reporter: dcicas, Unassigned)

Details

(Keywords: regressionwindow-wanted)

Attachments

(2 files)

Attached image native playback bug.PNG

[Note]:

  • This issue appeared sometime last week (18-22 Feb) because the video player worked perfectly before last week. So I assume something had to happen along the native playback (theoplayer).
  • This issue only occurs on Win 7 both x86 and x64.
  • The website works on chrome.

[Affected versions]:

  • Fx 67.0a1 BuildId: 20190225102402
  • Fx 66.0b10 BuildId: 20190221160854
  • Fx 65.0.1 BuildId: 20190211233335
  • Fx 60.0b16 BuildId: 20180426170554

[Affected platforms]:

  • Win 7 x86 and x64

[Steps to reproduce]:

  1. Reach https://edition.cnn.com/videos
  2. Play the video.

[Expected result]:

  • The video is played without any errors.

[Actual result]:

  • The video does not start and the message "something went wrong during native playback"

[Regression range]:

  • I will come back with the regression range ASAP.

[Additional notes]:

  • This issue appeared sometime last week (18-22 Feb) because the video player worked perfectly before last week. So I assume something had to happen along the native playback (theoplayer).
  • This issue only occurs on Win 7 both x86 and x64.
  • The website works on chrome.
Priority: -- → P2
Has Regression Range: --- → no

Daniel, could you provide a regression window please? Thanks

Flags: needinfo?(daniel.cicas)

Hello,

I tried all morning to find a regression range but to no avail. I went back as far as 2017 December builds and each one had this bug which is odd because 2 weeks ago everything was working fine (I tested every FX 66 Beta builds using the website in question and it worked fine).

Maybe my media packs on Win 7 went out of date all of a sudden or removed some support for old media packs. If you have any questions feel free to ask!

Flags: needinfo?(daniel.cicas) → needinfo?(pascalc)

I have attempted to reproduce the issue myself on a 64-bit Windows 7, but I could not. These are my results:

  • Firefox ESR (v60.6.1) -> working just fine.
  • Firefox Release (v66.0.3) -> not working correctly, but showing different error messages in the Browser Console.
    (I will attach the error messages as a text file to this bug)
  • Firefox Beta (v67.0b9) -> working just fine.
  • Firefox nightly (v68.0a1) -> working just fine.

Daniel Cicas, can you please confirm this reproduction on the original test machine?

Flags: needinfo?(daniel.cicas)

These are the error messages displayed when opening the test link on Firefox Release v66.0.3 on Windows 7 x64, as mentioned in the previous comment.

QA Whiteboard: [qa-regression-triage]

Hello,

Yes I could reproduce this issue with the original machine on Fx 67.0b10. I received a prompt to update Windows Feature Media Pack and after updating the issue disappeared.

Most probably the issue was caused by my version of Windows Feature Media Pack being out of date, as I said in Comment 2.

Flags: needinfo?(daniel.cicas)
Flags: needinfo?(pascalc)

I will mark this as WORKSFORME based on comment 3 and comment 5.

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: