Re: CfC: publish Proposed Recommendation of Web Messaging; deadline March 28

Den 3/24/2015 20:37, Arthur Barstow skreiv: On 3/21/15 1:27 PM, Jonas Sicking wrote: On Sat, Mar 21, 2015 at 5:52 AM, Arthur Barstow wrote: 2.; this test failure (which passes on IE) is considered an implementation bug (MessageChanne

Re: Adopting postMessage and MessageChannel from HTML5?

On 1/9/2010 23:05, Ian Hickson wrote: > On Sat, 9 Jan 2010, Sigbjorn Finne wrote: > >> On 1/9/2010 09:00, Ian Hickson wrote: >> >>> Would this working group be interested in adopting the >>> Window.postMessage and MessageChannel/MessagePort features fr

Re: Adopting postMessage and MessageChannel from HTML5?

On 1/9/2010 09:00, Ian Hickson wrote: > Would this working group be interested in adopting the Window.postMessage > and MessageChannel/MessagePort features from HTML5? It was recently split > from the main HTML5 spec into a subspec, but some people have suggested it > might be best in the webapp

[widgets] element processing

Hi, I noticed a minor inconsistency while reading through the latest Editor's Draft (2009-05-08) of the "Packaging and Configuration" specification: the processing section (Section 9) step 7 has an "at-most-one" semantics for processing elements. That's inconsistent with 8.12 (zero or more),