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

Adam Barth w3c at adambarth.com
Thu Jul 15 13:44:56 PDT 2010

On Thu, Jul 15, 2010 at 5:24 AM, Boris Zbarsky <bzbarsky at mit.edu> wrote:
> On 7/15/10 8:13 AM, Simon Pieters wrote:
>> Do you think the special value "/" is a good enough replacement for
>> location.href as the targetOrigin to remove the ability to pass in a
>> path in Gecko?
> I don't know.  It's good enough for me on technical grounds; I can't speak
> to compat issues or existing levels of deployment, since I haven't been
> following that part of things.  I've only dealt with postMessage as an API
> consumer, not an implementor...

I don't see the benefits of these changes outweighing the cost of
changing current implementations.  As an implementor, you'd be
training me to not implement HTML5 features and, as an author, you'd
be training me to not use HTML5 features.


More information about the whatwg mailing list