<html>
<head>
<base href="https://bugs.webkit.org/" />
</head>
<body>
<p>
<div>
<b><a class="bz_bug_link
bz_status_NEW "
title="NEW - REGRESSION (STP 4): Unable to target pseudo element webkit-media-controls"
href="https://bugs.webkit.org/show_bug.cgi?id=157635#c5">Comment # 5</a>
on <a class="bz_bug_link
bz_status_NEW "
title="NEW - REGRESSION (STP 4): Unable to target pseudo element webkit-media-controls"
href="https://bugs.webkit.org/show_bug.cgi?id=157635">bug 157635</a>
from <span class="vcard"><a class="email" href="mailto:jer.noble@apple.com" title="Jer Noble <jer.noble@apple.com>"> <span class="fn">Jer Noble</span></a>
</span></b>
<pre>(In reply to <a href="show_bug.cgi?id=157635#c4">comment #4</a>)
<span class="quote">> They will. We always provide the default controls if JS is disabled.</span >
To be clear, this is a requirement of the HMTL specification:
<<a href="https://html.spec.whatwg.org/multipage/embedded-content.html#expose-a-user-interface-to-the-user">https://html.spec.whatwg.org/multipage/embedded-content.html#expose-a-user-interface-to-the-user</a>>
"If the [controls] attribute is present, or if scripting is disabled for the media element, then the user agent should expose a user interface to the user. This user interface should include features to begin playback, pause playback, seek to an arbitrary position in the content (if the content supports arbitrary seeking), change the volume, change the display of closed captions or embedded sign-language tracks, select different audio tracks or turn on audio descriptions, and show the media content in manners more suitable to the user (e.g. fullscreen video or in an independent resizable window). Other controls may also be made available."</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>