[whatwg] postMessage's target origin argument can be a full URL in some implementations
ian at hixie.ch
Mon Nov 15 15:25:41 PST 2010
On Wed, 11 Aug 2010, Boris Zbarsky wrote:
> On 8/10/10 9:11 PM, Ian Hickson wrote:
> > Specifically, this means the magic "/" string is no longer supported
> Why? That seemed like a useful feature, and not something likely to
> break anyone out there....
> In particular, it allows use cases that are not possible right now (e.g.
> reasonable postMessage from an about:blank page to a page that has the
> same origin as the about:blank page).
On Tue, 10 Aug 2010, Adam Barth wrote:
> Yeah, it seems like there's a big difference between breaking changes
> (e.g., rejecting previously valid inputs) and non-breaking changes
> (e.g., allowing some new, previously invalid inputs).
On Wed, 11 Aug 2010, Sigbjorn Finne wrote:
> Opera has reverted targetOrigin validation back to previous in current
> builds, but we also wouldn't mind keeping "/".
On Thu, 12 Aug 2010, Hallvord R M Steen wrote:
> I stated somewhere that reverting the path validation stuff should
> include removing the magic '/' feature, given this use case it was
> probably better to keep '/'.
I have returned the '/' feature to its former glory without readding the
URL path restriction.
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
More information about the whatwg