@zcorpan IMHO, no. One of the benefits of allowing video-in-an-img is the dramatic reduction in power use due to broad hardware decoder availability. That benefit is largely absent for AVIF content on existing hardware.
@tomayac@hochsays@cwilso@kosamari@DasSurma Yeah, WebAudio uses the same rules on iOS as things like game audio: it obeys the mute switch on iPhones, but will play over headphones regardless of the mute switch.
@2co_p @bradeeoh WKWebView is used by more than just browsers; changing the default behavior would break those apps. And even among browsers, different browsers have different rules and policies. If you want the exact behavior of Safari, consider using SFSafariViewController instead of WKWebView.
@2co_p @bradeeoh Yes, the mistake in your project was configuring your WKWebView to not require a user gesture to play audible media types.
CSS rules do not affect fullscreen video presentation. You cannot transform, rotate, absolutely position, or change the display mode of video in fullscreen
@2co_p @bradeeoh display:none won’t keep a video from playing in fullscreen, even in iOS Safari. What _will_ keep a video from playing in fullscreen is iOS Safari’s autoplay rules.
@ChristianSelig If you wouldn’t mind, please file a report at https://t.co/xKk6tRQL0B. I’d be happy to TAL, as WebKit is also an AVFoundation client in Mac Catalyst apps.
@ChristianSelig @bradeeoh @smfr@hortont424 Lol, sounds like an application of “Noble’s Lemma”: “If something weird is happening, it’s probably something you did.”
(Except people are usually saying it to me, so it’s more like: “…it’s probably something Jer did.”)
@marcoarment@liscio As far as what content sounds worse, I don’t have a clear answer. From the samples I’ve been listening to, music and speech sound approximately equally bad, with speech sounding robotic and with music nearly dropping entire instruments.
@marcoarment@liscio And now Netflix has added UI for non-1x playback.
Anecdotally, I suspect between YouTube and Netflix, harmonic content is probably more commonly played at non-1x rates, but I have no data to back that up.
@marcoarment@liscio That’s certainly possible! When we made this decision at first, YouTube was the primary user of non-default-rate playback in the wild. A lot has changed since then.
I’m wary of just flip-flopping what use cases get the short end of the stick, though.