Bug 243155
Summary: | The HTMLAudioElement works only with JS enabled | ||
---|---|---|---|
Product: | WebKit | Reporter: | Dimitrios Grammatikogiannis <d.grammatiko> |
Component: | Media | Assignee: | Nobody <webkit-unassigned> |
Status: | RESOLVED DUPLICATE | ||
Severity: | Normal | CC: | cdumez, graouts, jcraig, jer.noble, karlcow, webkit-bug-importer |
Priority: | P2 | Keywords: | BrowserCompat, InRadar |
Version: | Safari 15 | ||
Hardware: | Unspecified | ||
OS: | macOS 12 | ||
URL: | https://dgrammatiko.netlify.app/blog/from-html-to-pwa/radio/ |
Dimitrios Grammatikogiannis
The audio element requires Javascript to have any meaningful interactivity (eg playback a live stream). This is odd as the detail element works without JS and also the other 2 engines (gecko and blink) seem quite happy playing a stream even without JS enabled.
The issue could be easily reproduced by disabling JS and visiting this url: https://dgrammatiko.netlify.app/blog/from-html-to-pwa/radio/
I'm guessing video element could also be unusable without JS, but I don't have any handy MP4 file to test it locally.
Attachments | ||
---|---|---|
Add attachment proposed patch, testcase, etc. |
Chris Dumez
Probably because our media controls are implemented using JS?
Source/WebCore/Modules/mediacontrols/mediaControlsBase.js
Source/WebCore/Modules/mediacontrols/mediaControlsApple.js
Source/WebCore/Modules/modern-media-controls/gesture-recognizers/gesture-recognizer.js
Source/WebCore/Modules/modern-media-controls/gesture-recognizers/pinch.js
Source/WebCore/Modules/modern-media-controls/gesture-recognizers/tap.js
Source/WebCore/Modules/modern-media-controls/controls/close-button.js
Source/WebCore/Modules/modern-media-controls/controls/layout-node.js
Source/WebCore/Modules/modern-media-controls/controls/overflow-button.js
[...]
Karl Dubost
Dimitrios
did you meet the issue on a big website?
Or did you need it in a specific user context and/or for developing an app?
Dimitrios Grammatikogiannis
> did you meet the issue on a big website? Or did you need it in a specific user context and/or for developing an app?
No, not really, I was writing a post about progressive enhancement and I was surprised that the native audio element was requiring JS to be enabled on Safari.
Probably this is not a high priority issue (or not an issue at all) I just felt that this might worth reporting.
Radar WebKit Bug Importer
<rdar://problem/97879513>
Sam Sneddon [:gsnedders]
*** Bug 178040 has been marked as a duplicate of this bug. ***
Sam Sneddon [:gsnedders]
*** This bug has been marked as a duplicate of bug 178040 ***