I'll suggest to remove the "url" attribute from PresentationSession due to: 1. There is no use case that cannot be achieve without this attribute. 2. The actual URL that loaded in presentation browsing context might changed after HTTP redirect. Additional control protocol is required for synchronizing the value between UAs if we want this attribute to reflect the window.location.href in presentation browsing context. Best Regards, Shih-Chiang Chien Mozilla Taiwan On Tue, Jun 2, 2015 at 8:13 AM, mark a. foltz <mfoltz@google.com> wrote: > This is seems to be a bug in the spec. Are there any objections to adding > a url attribute to PresentationSession, that would be set to the URL that > was used to start or join the presentation? > > m. > > > On Mon, Jun 1, 2015 at 8:06 AM, Oleg Beletski <o.beletski@samsung.com> > wrote: > >> Hello, >> >> I noticed that in the part of the document describing starting of a >> presentation session [2] there is a reference to the url attribute of the >> PresentationSession and that attribute is not a part of PresentationSession >> interface [1]. Is that a bug in the spec? The same issue repeats in couple >> of more places in the spec. >> >> "Create a new PresentationSession S. >> Set S.url to presentationUrl, set S.id to I, and set S.state to >> disconnected." >> >> [1] http://w3c.github.io/presentation-api/#interface-presentationsession >> [2] >> http://w3c.github.io/presentation-api/#starting-a-presentation-session >> >> Best regards, >> Oleg >> >> >> >
Received on Tuesday, 2 June 2015 12:20:44 UTC