RE: postMessage feedback

Quick follow up question on XDM.

Ian wrote "Done"
in reply to
On Tue, 22 Apr 2008, Jeff Walden wrote:
>
> Make the targetOrigin argument non-optional.  "*" would mean "don't
> care" while anything else would specify an origin (or result in a syntax
> error).  If this is done, it's no longer possible to have
> time-of-check/time-of-use issues (in the async case) without the web
> developer explicitly choosing to do so.  This change shouldn't be any
> more than 5-10 lines, and fixing existing testcases to adjust for this
> change is straightforward.

I didn’t quite get how the TOC-TOU issue can happen here? Can we elaborate.


> -----Original Message-----
> From: Ian Hickson [mailto:ian@hixie.ch]
> Sent: Monday, April 28, 2008 2:06 PM
> To: Sunava Dutta
> Cc: Chris Wilson; IE8 Core AJAX SWAT Team; public-html-comments@w3.org
> Subject: RE: postMessage feedback
>
> On Mon, 28 Apr 2008, Sunava Dutta wrote:
> >
> > I followed the threads and mentioned that I’d touch base with my team
> > and get back with our position.
> > http://lists.w3.org/Archives/Public/public-html-

> comments/2008Apr/0029.html
> > However, it seems that my comment here has been overlooked.
>
> Actually that e-mail was carefully considered when I responded to the
> postMessage() feedback, as you can see by searching for "I agree with
> Jonas." in my reply:
>
>    http://lists.w3.org/Archives/Public/public-html/2008Apr/0753.html

>
> Is there a part of the message that I overlooked? I apologise if that
> is
> the case; let me know what it is you would like changed in the spec and
> I
> will look at it again.
>
>
> > I’m aware we’ve been having discussions on the topic but changing
> > the spec took me by surprise.
>
> Discussions usually lead to changes. :-)
>
>
> > We want to get the latest technology out to the web developer as soon
> as
> > possible with cross document messaging. That said, for browsers it is
> > challenging enough given that it’s a draft and consequently a work in
> > progress. Having associated timelines/expectations set regarding
> changes
> > and updates would be really helpful.
> >
> > In addition, can we have an email to the group with a list of topics
> for
> > cross document messaging that are being discussed/in flux and the
> > (tentative) timelines for resolving them?
>
> At this point the spec is pretty stable. There is no outstanding
> feedback,
> and there are no known issues (other than a minor one to do with the
> serialisation of origin tuples, but the example shows how that is
> supposed
> to look).
>
> The status of each section in the spec is given by the annotation at
> the
> start of the section in the spec, the documentation for which is here:
>
>    http://www.whatwg.org/specs/web-apps/current-work/status-

> documentation.html
>
> For example, the Cross-Document Messaging section:
>
>    http://www.whatwg.org/specs/web-apps/current-

> work/#crossDocumentMessages
>
> ...has the status "Awaiting implementation feedback", which is defined
> to
> mean "The section is basically done, but might change in response to
> feedback from implementors. Major changes are unlikely past this point
> unless it is found that the feature, as specified, really doesn't work
> well". As you can see from the annotation, all the browsers are marked
> as
> implementing the feature to some extent.
>
> (By the way, the icon I was using for IE recently changed to be some
> sort
> of sun icon. If you have a 16x16 icon I should use instead, please let
> me
> know. The same goes for Opera and Safari, both of which right now have
> icons that aren't 16x16 or that aren't ideal for some reason.)
>
> The list of pending feedback is here:
>
>    http://www.whatwg.org/issues/

>
> Cheers,
> --
> Ian Hickson               U+1047E                )\._.,--....,'``.
> fL
> http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._
> ,.
> Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-
> .;.'

Received on Monday, 16 June 2008 23:12:19 UTC