Bobby Holley
09834cc4d8
Bug 754202 - Fix content->chrome postMessage mochitest. r=bz
...
This isn't something we actually support, and were using enablePrivilege to do it before.
When we switch this to SpecialPowers wrapping, the sender origin becomes a chrome URL (not
very interesting) and the source window becomes null (which we do explicitly in
nsGlobalWindow for chrome callers). So those tests stop being useful.
2012-06-07 14:28:21 +02:00
Jonas Sicking
6c6a7cea3e
Disallow content access to chrome functions without __exposedProps__ (bug 628410, r=gal).
2011-01-29 18:47:17 -08:00
Mounir Lamouri
cc33a99998
Merging to tip. a=blocking-b7
2010-09-30 17:10:19 -07:00
jwalden@mit.edu
cea0828eea
Bug 430251 - Update to latest HTML5 and make postMessage dispatch its event asynchronously, as well as dispatch at the window, not the document. r=jst, r=smaug, sr=sicking, a=damons, c=cookie
2008-05-02 12:26:47 -07:00
jwalden@mit.edu
5809da44ed
Bug 417075 - Update postMessage and MessageEvent to reflect domain/uri being replaced by origin, optional origin argument. r+sr=sicking, a=beltzner
2008-02-26 19:48:54 -08:00
jwalden@mit.edu
035ea5179c
Bug 387706 - Implement HTML5's cross-document messaging API (postMessage), enabling secure cross-origin communication between windows. r+sr=sicking, sr=jst, a=jst
2008-01-29 17:31:29 -08:00
