W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2010

[whatwg] postMessage's target origin argument can be a full URL in some implementations

From: Sigbjorn Finne <sigbjorn.finne@gmail.com>
Date: Wed, 11 Aug 2010 20:22:11 +0200
Message-ID: <4C62EA53.9020208@gmail.com>
On 8/11/2010 06:58, Adam Barth wrote:
> On Tue, Aug 10, 2010 at 9:28 PM, Boris Zbarsky <bzbarsky at mit.edu> 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).
>>     
>
> 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).
>
>   

Opera has reverted targetOrigin validation back to previous in current 
builds, but we also wouldn't mind keeping "/".

--sigbjorn; sof at opera.com
Received on Wednesday, 11 August 2010 11:22:11 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:59 UTC