13083 2011-06-29 06:58:27 +0000 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. 2011-08-04 21:29:49 +0000 1 1 1 Unclassified WebAppsWG Web Messaging (editor: Ian Hickson) unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#posting-messages P3 normal --- 1 contributor ian ian jackalmage jonas mike public-webapps public-webapps-bugzilla oldest_to_newest 50444 0 contributor 2011-06-29 06:58:27 +0000 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) 50445 1 jonas 2011-06-29 07:02:47 +0000 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. 50461 2 jackalmage 2011-06-29 18:23:30 +0000 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. 54193 3 ian 2011-08-04 21:29:49 +0000 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.