Chargement du reste de cette comparaison.

Untitled diff

Créé Le diff n'expire jamais
105 suppressions
339 lignes
126 ajouts
352 lignes
W3C
W3C
HTML5 Web Messaging
HTML5 Web Messaging
W3C Candidate Recommendation 01 May 2012
W3C Proposed Recommendation 07 April 2015
This Version:
This Version:
http://www.w3.org/TR/2012/CR-webmessaging-20120501/
http://www.w3.org/TR/2015/PR-webmessaging-20150407/
Latest Published Version:
Latest Published Version:
http://www.w3.org/TR/webmessaging/
http://www.w3.org/TR/webmessaging/
Latest Editor's Draft:
Latest Editor's Draft:
http://dev.w3.org/html5/postmsg/
http://dev.w3.org/html5/postmsg/
Test suite:
https://github.com/w3c/web-platform-tests/tree/master/webmessaging
Implementation report:
https://w3c.github.io/test-results/webmessaging/all
Previous Versions:
Previous Versions:
http://www.w3.org/TR/2012/CR-webmessaging-20120501/
http://www.w3.org/TR/2012/WD-webmessaging-20120313/
http://www.w3.org/TR/2012/WD-webmessaging-20120313/
http://www.w3.org/TR/2011/WD-webmessaging-20111020/
http://www.w3.org/TR/2011/WD-webmessaging-20111020/
http://www.w3.org/TR/2011/WD-webmessaging-20110317/
http://www.w3.org/TR/2011/WD-webmessaging-20110317/
http://www.w3.org/TR/2010/WD-webmessaging-20101118/
http://www.w3.org/TR/2010/WD-webmessaging-20101118/
Editor:
Editor:
Ian Hickson, Google, Inc.
Ian Hickson, Google, Inc.
Copyright © 2012 W3C® (MIT, ERCIM, Keio), All Rights Reserved. W3C liability, trademark and document use rules apply.
Copyright © 2015 W3C® (MIT, ERCIM,Keio, Beihang). W3C liability, trademark and document use rules apply.
The bulk of the text of this specification is also available in the WHATWG Web Applications 1.0 specification, under a license that permits reuse of the specification text.
The bulk of the text of this specification is also available in the WHATWG HTML specification, under a license that permits reuse of the specification text.
Abstract
Abstract
This specification defines two mechanisms for communicating between browsing contexts in HTML documents.
This specification defines two mechanisms for communicating between browsing contexts in HTML documents.
Status of This document
Status of This document
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
This section describes the status of this document at the time of its publication. Other documents may supersede this document. A list of current W3C publications and the latest revision of this technical report can be found in the W3C technical reports index at http://www.w3.org/TR/.
If you wish to make comments regarding this document in a manner that is tracked by the W3C, please submit them via using our public bug database. If you do not have an account then you can enter feedback using this form:
This specification is the 7 April 2015 Proposed Recommendation of HTML5 Web Messaging. The W3C Web Applications Working Group is the W3C working group responsible for this specification's progress along the W3C Recommendation track. This document is intended to become a W3C Recommendation. A Candidate Recommendation (CR) of the specification was published on 01 May 2012.
Feedback Comments
Please enter your feedback, carefully indicating the title of the section for which you are submitting feedback, quoting the text that's wrong today if appropriate. If you're suggesting a new feature, it's really important to say what the problem you're trying to solve is. That's more important than the solution, in fact.
During the CR review period, the initMessageEvent() method was added to the MessageEvent interface, the source of MessageEventInit was extended to WindowProxy or MessagePort, also there are some updates to this document's References appendix.
A Test Suite and Implementation Report for this specification are available.
Please don't use section numbers as these tend to change rapidly and make your feedback harder to understand.
The W3C Membership and other interested parties are invited to review the document and send comments to public-webapps@w3.org (subscribe, archives) through 7 May 2015. Advisory Committee Representatives should consult their WBS questionnaires.
(Note: Your IP address and user agent will be publicly recorded for spam prevention purposes.)
You can also e-mail feedback to public-webapps@w3.org (subscribe, archives), or whatwg@whatwg.org (subscribe, archives). All feedback is welcome.
If you wish to make comments regarding this document in a manner that is tracked by the W3C, please submit them using our public bug database. You can also e-mail feedback to public-webapps@w3.org (subscribe, archives), or whatwg@whatwg.org (subscribe, archives). All feedback is welcome.
Notifications of changes to this specification are sent along with notifications of changes to related specifications using the following mechanisms:
Publication as a Proposed Recommendation does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
E-mail notifications of changes
Commit-Watchers mailing list (complete source diffs): http://lists.whatwg.org/listinfo.cgi/commit-watchers-whatwg.org
Browsable version-control record of all changes:
CVSWeb interface with side-by-side diffs: http://dev.w3.org/cvsweb/html5/
Annotated summary with unified diffs: http://html5.org/tools/web-apps-tracker
Raw Subversion interface: svn checkout http://svn.whatwg.org/webapps/
The W3C Web Applications Working Group is the W3C working group responsible for this specification's progress along the W3C Recommendation track. This specification is the 01 May 2012 Candidate Recommendation. Comments for the 13 March 2012 Last Call Working Draft are tracked in the comment tracking document.
By publishing this Proposed Recommendation, W3C expects the functionality specified in this Proposed Recommendation will not be affected by changes to DOM4, Web IDL or Web Workers as those specifications proceed to Recommendation.
This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
This document was produced by a group operating under the 5 February 2004 W3C Patent Policy. W3C maintains a public list of any patent disclosures made in connection with the deliverables of the group; that page also includes instructions for disclosing a patent. An individual who has actual knowledge of a patent which the individual believes contains Essential Claim(s) must disclose the information in accordance with section 6 of the W3C Patent Policy.
Candidate Recommendation Exit Criteria
To exit the Candidate Recommendation (CR) stage, the following criteria must have been met:
There will be at least two interoperable implementations passing all approved test cases in the test suite for this specification. An implementation is to be available (i.e. for download), shipping (i.e. not private), and not experimental (i.e. intended for a wide audience). The working group will decide when the test suite is of sufficient quality to test interoperability and will produce an implementation report (hosted together with the test suite).
A minimum of three months of the CR stage will have elapsed (i.e. not until after 01 August 2012). This is to ensure that enough time is given for any remaining major errors to be caught. The CR period will be extended if implementations are slow to appear.
Publication as a Candidate Recommendation does not imply endorsement by the W3C Membership. This is a draft document and may be updated, replaced or obsoleted by other documents at any time. It is inappropriate to cite this document as other than work in progress.
This document is governed by the 14 October 2005 W3C Process Document.
Table of Contents
Table of Contents
1 Conformance requirements
1 Conformance requirements
1.1 Dependencies
1.1 Dependencies
2 Terminology
2 Terminology
3 Event definitions
3 The MessageEvent interfaces
4 Cross-document messaging
4 Cross-document messaging
4.1 Introduction
4.1 Introduction
4.2 Security
4.2 Security
4.2.1 Authors
4.2.1 Authors
4.2.2 User agents
4.2.2 User agents
4.3 Posting messages
4.3 Posting messages
5 Channel messaging
5 Channel messaging
5.1 Introduction
5.1 Introduction
5.1.1 Ports as the basis of an object-capability model on the Web
5.1.1 Examples
5.1.2 Ports as the basis of an object-capability model on the Web
5.1.2 Ports as the basis of abstracting out service implementations
5.1.3 Ports as the basis of abstracting out service implementations
5.2 Message channels
5.2 Message channels
5.3 Message ports
5.3 Message ports
5.3.1 Ports and garbage collection
5.4 Ports and garbage collection
References
References
Acknowledgements
Acknowledgements
1 Conformance requirements
1 Conformance requirements
All diagrams, examples, and notes in this specification are non-normative, as are all sections explicitly marked non-normative. Everything else in this specification is normative.
All diagrams, examples, and notes in this specification are non-normative, as are all sections explicitly marked non-normative. Everything else in this specification is normative.
The key words "MUST", "MUST NOT", "REQUIRED", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in the normative parts of this document are to be interpreted as described in RFC2119. For readability, these words do not appear in all uppercase letters in this specification. [RFC2119]
The key words "MUST", "MUST NOT", "REQUIRED", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in the normative parts of this document are to be interpreted as described in RFC2119. For readability, these words do not appear in all uppercase letters in this specification. [RFC2119]
Requirements phrased in the imperative as part of algorithms (such as "strip any leading space characters" or "return false and abort these steps") are to be interpreted with the meaning of the key word ("must", "should", "may", etc) used in introducing the algorithm.
Requirements phrased in the imperative as part of algorithms (such as "strip any leading space characters" or "return false and abort these steps") are to be interpreted with the meaning of the key word ("must", "should", "may", etc) used in introducing the algorithm.
Some conformance requirements are phrased as requirements on attributes, methods or objects. Such requirements are to be interpreted as requirements on user agents.
Some conformance requirements are phrased as requirements on attributes, methods or objects. Such requirements are to be interpreted as requirements on user agents.
Conformance requirements phrased as algorithms or specific steps may be implemented in any manner, so long as the end result is equivalent. (In particular, the algorithms defined in this specification are intended to be easy to follow, and not intended to be performant.)
Conformance requirements phrased as algorithms or specific steps may be implemented in any manner, so long as the end result is equivalent. (In particular, the algorithms defined in this specification are intended to be easy to follow, and not intended to be performant.)