Open Bug 1915097 Opened 2 months ago Updated 23 days ago

www.netflix.com - Videos fail to play when in desktop mode

Categories

(Web Compatibility :: Site Reports, defect, P3)

ARM
Android

Tracking

(Not tracked)

People

(Reporter: rbucata, Unassigned)

References

()

Details

(Keywords: webcompat:blocked, webcompat:site-report, Whiteboard: [webcompat-source:web-bugs])

User Story

platform:android
impact:site-broken
configuration:general
affects:few
branch:release
diagnosis-team:media

Environment:
Operating system: Android
Firefox version: Firefox 123.1.0 Mobile

Preconditions:
Desktop mode enabled

Steps to reproduce:

  1. Navigate to: https://www.netflix.com and perform account login
  2. Select a show and play it
  3. Observe

Expected Behavior:
Video plays

Actual Behavior:
Video fails to play in desktop mode

Notes:

  • Reproduces regardless of the status of ETP
  • Reproduces in Firefox Nightly, and Firefox Release
  • Does not reproduce in Chrome

Created from https://github.com/webcompat/web-bugs/issues/134526

This is only a problem on Android as I understand it.

User Story: (updated)

I'm also getting "Pardon the interruption" screen. on Firefox nightly on windows 10, since Friday, including 2x Nightly upgrades.
Slightly different error though: F7121-1331 on this page: https://help.netflix.com/en/node/100151?accordionCategory=windows_computer,
And E100 on the "Pardon the interruption" screen.
I can open another bug, if this seems to be too different from the Android one.

Actually for desktop, this bug more closely matches the error I get: bug# 1763811
But why would I be hit by a 2-year old bug now: I watch video regularly on this browser typically every week.

Severity: -- → S2
User Story: (updated)
User Story: (updated)
Severity: S2 → S4
Priority: P1 → P3

I don't think we need to be too concerned about desktop mode support. Might be interesting to look at some telemetry to know how common that is though to be sure.

This is almost guaranteed to be intentional, we'll need to contact Netflix to be sure.

You need to log in before you can comment on or make changes to this bug.