This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 18248 - <video> should allow UAs to "expose a user interface to the user" if the user asks for it (e.g. from the context menu, which several browsers support)
Summary: <video> should allow UAs to "expose a user interface to the user" if the user...
Status: RESOLVED FIXED
Alias: None
Product: HTML WG
Classification: Unclassified
Component: HTML5 spec (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Silvia Pfeiffer
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-18 17:49 UTC by contributor
Modified: 2012-10-21 22:31 UTC (History)
8 users (show)

See Also:


Attachments

Description contributor 2012-07-18 17:49:48 UTC
This was was cloned from bug 17553 as part of operation convergence.
Originally filed: 2012-06-20 06:04:00 +0000

================================================================================
 #0   contributor@whatwg.org                          2012-06-20 06:04:51 +0000 
--------------------------------------------------------------------------------
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/the-video-element.html
Multipage: http://www.whatwg.org/C#expose-a-user-interface-to-the-user
Complete: http://www.whatwg.org/c#expose-a-user-interface-to-the-user

Comment:
<video> should allow UAs to "expose a user interface to the user" if the user
asks for it (e.g. from the context menu, which several browsers support)

Posted from: 85.227.159.48 by simonp@opera.com
User agent: Opera/9.80 (Macintosh; Intel Mac OS X 10.7.3; U; en) Presto/2.10.229 Version/11.64
================================================================================
Comment 1 Robin Berjon 2012-09-11 14:55:57 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are
satisfied with this response, please change the state of this bug to CLOSED. If
you have additional information and would like the Editor to reconsider, please
reopen this bug. If you would like to escalate the issue to the full HTML
Working Group, please add the TrackerRequest keyword to this bug, and suggest
title and text for the Tracker Issue; or you may create a Tracker Issue
yourself, if you are able to do so. For more details, see this document:

   http://dev.w3.org/html5/decision-policy/decision-policy.html

Status: Accepted
Rationale: Change already made.
Comment 2 Silvia Pfeiffer 2012-10-15 06:24:30 UTC
Reopening:
I'm unhappy with this resolution. I prefer to apply the patch that was applied to the WHATWG spec, since it provides more flexibility, in particular for accessibility:
https://github.com/w3c/html/commit/0d00c77f8bd9e0b10ec36323dc908e2a9a37dc2c
Comment 3 Robin Berjon 2012-10-15 08:41:14 UTC
(In reply to comment #2)
> Reopening:
> I'm unhappy with this resolution. I prefer to apply the patch that was
> applied to the WHATWG spec, since it provides more flexibility, in
> particular for accessibility:
> https://github.com/w3c/html/commit/0d00c77f8bd9e0b10ec36323dc908e2a9a37dc2c

Sure — just because the existing spec may be considered "good enough" to resolve doesn't mean we can't take improvements!
Comment 4 Edward O'Connor 2012-10-17 22:23:23 UTC
Silvia, do you plan to apply the change you referred to?
Comment 5 Silvia Pfeiffer 2012-10-17 22:46:04 UTC
Yes, next weekend. I only apply patches once a week. Between that I give people time to give me feedback.
Comment 6 Silvia Pfeiffer 2012-10-21 22:31:38 UTC
EDITOR'S RESPONSE: This is an Editor's Response to your comment. If
you are satisfied with this response, please change the state of
this bug to CLOSED. If you have additional information and would
like the Editor to reconsider, please reopen this bug. If you would
like to escalate the issue to the full HTML Working Group, please
add the TrackerRequest keyword to this bug, and suggest title and
text for the Tracker Issue; or you may create a Tracker Issue
yourself, if you are able to do so. For more details, see this
document:   http://dev.w3.org/html5/decision-policy/decision-policy-v2.html

Status: Accepted

Change Description:
https://github.com/w3c/html/commit/0d00c77f8bd9e0b10ec36323dc908e2a9a37dc2c

Rationale: Adopted WHATWG patch