Open Bug 1941766 Opened 1 month ago Updated 20 days ago

www.espncricinfo.com - Choppy playback of the videos

Categories

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

Firefox 136
ARM
Android

Tracking

(Webcompat Priority:P2, firefox134 affected, firefox135 affected, firefox136 affected)

Webcompat Priority P2
Tracking Status
firefox134 --- affected
firefox135 --- affected
firefox136 --- affected

People

(Reporter: ctanase, Unassigned, NeedInfo)

References

()

Details

(Keywords: webcompat:needs-diagnosis, webcompat:site-report, Whiteboard: [webcompat-source:web-bugs][webcompat:sightline])

User Story

platform:android
impact:content-missing
configuration:general
affects:all
branch:release
diagnosis-team:media

Attachments

(1 file)

Environment:
Operating system: Android 14
Firefox version: Firefox Mobile 135.0/134/136

Steps to reproduce:

  1. Go to https://www.espncricinfo.com/cricket-videos/rohit-sharma-seen-training-with-mumbai-ranji-trophy-squad-1468975
  2. Play the video.
  3. Observe the behavior.

Expected Behavior:
The video plays smoothly.

Actual Behavior:
The video playback is laggy/choppy.

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/145696

Attached video FF vs Chrome.mp4
Version: unspecified → Firefox 136

Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.

Whiteboard: [webcompat-source:web-bugs] → [webcompat-source:web-bugs][webcompat:sightline]
Severity: -- → S3
User Story: (updated)
Priority: -- → P2

This looks like a typical bug we get in media where something doesn't play as well as it might in other browsers. Is this really webcompat, or simply a media bug that should get filed under the media component and end up getting queued in our normal bug triage process? Seems like we're starting to blur the line between 'firefox not supported' bugs and typical media playback bugs.

Flags: needinfo?(dschubert)

(In reply to Jim Mathies [:jimm] from comment #3)

Seems like we're starting to blur the line between 'firefox not supported' bugs and typical media playback bugs.

Web Compatibility, from our point of view, is everything that falls into "something works in other browsers, but is broken in Firefox". Or, worded differently, everything that makes users use another browser to get something done - regardless of what that "something" is. Here, from the looks of it, the video is effectively unwatchable in Firefox, so users would have to use another browser, and that's bad.

The goal of diagnosis is to figure out what exactly is causing this. Right now, we just know "playback is choppy", but don't know why. Figuring out why is the "diagnosis" portion of this bug. If there is a Media Playback bug for this, then you can mark this as a webcompat:platform-bug, and set the "depends on" field to that core bug, at which point work here would be done - and that media core bug would now show up as affecting WebCompat. If we don't know why it's choppy in this case, we should figure it out - and either file a new core bug for this, or if the core bug is very specific to this one case, we can also just move this bug into a core component and attach a patch here.

Does that answer your question? I'm also happy to have a more elaborate chat or a call on this if you want.

Flags: needinfo?(dschubert)

I wasn't able to repro this on nightly or stable. Here's a profile from my device on nightly where I didn't have any issues. Would you be able to provide us with a profile recorded with the media preset?

Flags: needinfo?(ctanase)

:jolin, could you please check if you have the stuttering on your device and share a profile if you do?

Flags: needinfo?(jolin)

Performance profile captured on OnePlus 6 A6000 (Android 11): https://share.firefox.dev/3E2bDmS

Note: It might reproduce on some device only, for example I tried playing the video on Google Pixel 5 (Android 14) and it remains stuck loading

EDIT: captured performance profile on Google pixel as well: https://share.firefox.dev/4h0K5wN

Flags: needinfo?(ctanase)

Thanks Calin! I checked the profiles and didn't see anything that stood out to me compared to the profile I captured on my side. Do you see anything :jolin?

I captured a media performance profile on a Pixel 5 running Android 14, but on this particular phone the video would not play. Here's the profile -

https://share.firefox.dev/40MhaGQ

js console had -

VIDEOJS: ERROR: (CODE:MEDIA_ERR_NETWORK undefined) The media could not be loaded, either because the server or network failed or because the format is not supported.
Object { code: "MEDIA_ERR_NETWORK", message: "The media could not be loaded, either because the server or network failed or because the format is not supported." }
dtci.video.min.js:19:106287
: J-PE-0 MP-PAB-MEDIA_ERR_NETWORK MEDIA_INTERNAL_PLAYER_ERR. Caused by
Object { type: "error", target: div#vjs_video_3.evp-player.video-js.video.cricinfo-video.vjs-touch-enabled.vjs-workinghover.vjs-v7.evp-new-ad-display.mobile-portrait.espn-endCard-small.docked-video.vjs-has-started.vjs_video_3-dimensions.vjs-seeking.vjs-playing.vjs-waiting.vjs-user-inactive.vjs-error.vjs-controls-disabled, relatedTarget: undefined, preventDefault: preventDefault(), defaultPrevented: false, stopPropagation: stopPropagation(), isPropagationStopped: n(), stopImmediatePropagation: stopImmediatePropagation(), isImmediatePropagationStopped: n()
, which: undefined, … }
espn-web-player-bundle.min.js:6:34623
: J-PE-0 MP-PAB-MEDIA_ERR_NETWORK MEDIA_INTERNAL_PLAYER_ERR. Caused by
Object { code: "MEDIA_ERR_NETWORK", message: "The media could not be loaded, either because the server or network failed or because the format is not supported." }
espn-web-player-bundle.min.js:6:34623
: J-PE-0 MP-PAB-MEDIA_ERR_NETWORK The media could not be loaded, either because the server or network failed or because the format is not supported.

Webcompat Priority: --- → P2
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: