W3C home > Mailing lists > Public > public-webapps@w3.org > January to March 2012

Re: connection ceremony for iframe postMessage communications

From: Ian Hickson <ian@hixie.ch>
Date: Mon, 13 Feb 2012 20:57:33 +0000 (UTC)
To: John J Barton <johnjbarton@johnjbarton.com>
cc: public-webapps <public-webapps@w3.org>
Message-ID: <Pine.LNX.4.64.1202132055590.10315@ps20323.dreamhostps.com>
On Fri, 10 Feb 2012, John J Barton wrote:
> >
> > Why would the connectivity part of this be the hard part?
> 
> Because the existing information on cross-domain iframe communications 
> is incomplete and written in terms few Web app developers understand, 
> the browser implementations are new and the error messages they emit are 
> puzzling. Solutions for same-domain cases don't work for cross-domain. 
> Async communications is hard to debug.

I agree with your described problems, but I don't see the link between 
them and adding yet more features to the platform.

The solution to "existing information on cross-domain iframe 
communications is incomplete" is to add more information. The solution to 
"existing information on cross-domain iframe communications is written in 
terms few Web app developers understand" is to write new information. The 
solution to "the browser implementations are new" is to wait. The solution 
to "the error messages they emit are puzzling" is to file bugs on the 
browsers with suggestions for how to improve them. Etc.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 13 February 2012 20:57:56 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:50 GMT