Re: [presentation-api] Specify whether properties of the Presentation are left undefined

I think the spec currently addresses this, although it could be more 
explicit:

> In a controlling user agent, the defaultRequest attribute must 
return the default presentation request if any, null otherwise.

> In a receiving user agent, the receiver attribute must return the 
PresentationReceiver instance associated with the receiving browsing 
context and created by the receiving user agent when the receiving 
browsing context is created. In any other browsing context, it must 
return null.

We should update the text to state that these properties are defined 
for both conformance classes, and that they return null in cases where
 the corresponding conformance class is not implemented.

-- 
GitHub Notification of comment by mfoltzgoogle
Please view or discuss this issue at 
https://github.com/w3c/presentation-api/issues/205#issuecomment-180549060
 using your GitHub account

Received on Friday, 5 February 2016 20:47:04 UTC