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 12857 - <video> "provided by script in the page via the server" is unclear
Summary: <video> "provided by script in the page via the server" is unclear
Status: RESOLVED NEEDSINFO
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 trivial
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-02 17:09 UTC by contributor
Modified: 2012-07-18 18:39 UTC (History)
2 users (show)

See Also:


Attachments

Description contributor 2011-06-02 17:09:10 UTC
Specification: http://www.whatwg.org/specs/web-apps/current-work/complete/video-conferencing-and-peer-to-peer-communication.html
Section: http://www.whatwg.org/specs/web-apps/current-work/complete.html#peer-to-peer-connections

Comment:
"provided by script in the page via the server" is unclear

Posted from: 212.183.107.51
User agent: Mozilla/5.0 (X11; U; Linux i686; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.215 Safari/534.10
Comment 1 Ian 'Hixie' Hickson 2011-06-15 06:26:08 UTC
I don't know how else to say it... "a signaling channel provided by script in the page via the server". It's exactly what it says: a signaling channel that a script in the page provides, which is routed via the server. Do you have any suggestions for clarifying it?
Comment 2 Ian 'Hixie' Hickson 2011-06-21 06:57:32 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: Did Not Understand Request
Change Description: no spec change
Rationale: see comment 1