Open Bug 1941273 Opened 27 days ago Updated 9 days ago

websdr.ru - No sound available

Categories

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

ARM
Android

Tracking

(Webcompat Score:5, Webcompat Priority:P3)

Webcompat Score 5
Webcompat Priority P3

People

(Reporter: railioaie, Unassigned)

References

()

Details

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

User Story

platform:android
impact:site-broken
configuration:general
affects:all
branch:release
diagnosis-team:media
user-impact-score:100

Environment:
Operating system: Android 14
Firefox version: Firefox Mobile 134.0

Preconditions:
Clean profile

Steps to reproduce:

  1. Navigate to: http://websdr.ru/m.html
  2. Observe

Expected Behavior:
There should be audio/sound

Actual Behavior:
There is no audio

Notes:

  • Reproduces regardless of the status of ETP
  • Reproduces in firefox-nightly, and firefox-release

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

This might be similar to bug 1917601, but let's confirm.

Severity: -- → S2
User Story: (updated)
Priority: -- → P3
See Also: → 1917601
User Story: (updated)

Looks like this could be an autoplay detection/permissions issue? On Fenix nightly with or without autoplay enabled in the settings menu I see:

An AudioContext was prevented from starting automatically. It must be created or resumed after a user gesture on the page.

Changing media.autoplay.default to 0 fixes the issue. On desktop it appears to be the same thing, though on desktop changing the autoplay in the settings menu works. I don't see the usual autoplay blocked indicator on either platform, and interacting with the page doesn't seem to cause a difference either.

Flags: needinfo?(dschubert)

We think this is on the sites side of things and is related to auto play. Suggest outreach or an intervention for this particular site.

I can't make this work on Chrome or Firefox desktop, I would check first if it work in Chrome mobile. The code looks like it has a small bug.

Webcompat Priority: --- → P2

Let's put this into the "maybe reach out eventually" pile given previous comments. It indeed just looks like broken code.

User Story: (updated)
Webcompat Priority: P2 → P3
Webcompat Score: --- → 5
Flags: needinfo?(dschubert)
You need to log in before you can comment on or make changes to this bug.