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 13083 - postMessage should have an optional parameter for a synchronous request. Cross-domain AJAX calls are enough of a problem that it merits a supported way of fixing it, and this could be it.
Summary: postMessage should have an optional parameter for a synchronous request. Cros...
Status: RESOLVED WONTFIX
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: Web Messaging (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: public-webapps-bugzilla
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-06-29 06:58 UTC by contributor
Modified: 2011-08-04 21:29 UTC (History)
5 users (show)

See Also:

Attachments

Description contributor 2011-06-29 06:58:27 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/comms.html#crossDocumentMessages
Multipage: http://www.whatwg.org/C#posting-messages
Complete: http://www.whatwg.org/c#posting-messages

Comment:
postMessage should have an optional parameter for a synchronous request.
Cross-domain AJAX calls are enough of a problem that it merits a supported way
of fixing it, and this could be it.

Posted from: 131.107.0.116
User agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0)
Comment 1 Jonas Sicking (Not reading bugmail) 2011-06-29 07:02:47 UTC 
Synchronous cross-domain postMessage would make it impossible to implement out-of-process iframes in a reliable way, so I don't think we should do this.
Comment 2 Tab Atkins Jr. 2011-06-29 18:23:30 UTC 
Plus, is cross-domain AJAX has problems, the correct way to address them is to fix cross-domain AJAX, not commandeer a different technology to work around the problems.
Comment 3 Ian 'Hixie' Hickson 2011-08-04 21:29:49 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: Rejected
Change Description: no spec change
Rationale: This is intentionally not synchronous.