Hi @rafael226, can you please explain the purpose of this PR?

Is it possible to play already while the player is still loading?

Hi @jcbrand, yes. The purpose is to avoid blocking the user's play intent while the audio element is still loading metadata.

The PR doesn't try to force playback before the browser has enough data. It only keeps the custom Play button enabled/focusable during the loading state, so a mouse click or keyboard Enter can call audio.play(). The browser will then either start when enough data is available, or reject/handle playback according to its normal media rules.

Before this change, is_loading made the Play button disabled, so the control disappeared from the keyboard interaction path even though loading is a temporary state, not an error. The button still remains disabled for actual audio errors via has_error.

So the practical intent is: loading should show a spinner/status, but should not make the Play control unavailable.