[Bug 12405] <video> There's a problem with overlaying a sign-language video and using native controls, because the overlaid video overlaps the native controls

http://www.w3.org/Bugs/Public/show_bug.cgi?id=12405

--- Comment #9 from Simon Pieters <simonp@opera.com> 2011-08-11 08:37:04 UTC ---
(In reply to comment #8)
> It doesn't say _what_ to do with the native controls. That's up to the UA. It
> could be an entirely separate window, for instance.

It says

"Whether a video element is exposing a user interface is not expected to affect
the size of the rendering; controls are expected to be overlaid with the page
content without causing any layout changes, and are expected to disappear when
the user does not need them."

What "overlaid with the page content" means is a bit unclear.

> Anyway, if the author is positioning the sign-language tracks, then he's almost
> certainly also going to want to do his own controls.

I don't see how that follows.

> Who's going to have time
> to do sign-language tracks but not custom UI?

Maybe somebody who prioritizes accessibility over custom UI? The native
controls give accessibility for free (assuming the browser got it right).
Getting accessibility right with custom controls is not for free.

> If he's not positioning the
> sign-language tracks (e.g. just putting them side-by-side) then it's not an
> issue.

Right. But it's common to overlay the sign-language track.

> I suppose I could mention the issue in the rendering section, so that
> implementors who read that section are aware of it, would that be satisfactory?

Mentioning a problem without solving it doesn't help much. We need to agree on
what the right solution is, and specify that.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.

Received on Thursday, 11 August 2011 08:37:05 UTC