{"action":"created","issue":{"url":"https://api.github.com/repos/w3c/presentation-api/issues/91","labels_url":"https://api.github.com/repos/w3c/presentation-api/issues/91/labels{/name}","comments_url":"https://api.github.com/repos/w3c/presentation-api/issues/91/comments","events_url":"https://api.github.com/repos/w3c/presentation-api/issues/91/events","html_url":"https://github.com/w3c/presentation-api/issues/91","id":80455409,"number":91,"title":"Separate interface for controlling page and presenting page","user":{"login":"schien","id":1792048,"avatar_url":"https://avatars.githubusercontent.com/u/1792048?v=3","gravatar_id":"","url":"https://api.github.com/users/schien","html_url":"https://github.com/schien","followers_url":"https://api.github.com/users/schien/followers","following_url":"https://api.github.com/users/schien/following{/other_user}","gists_url":"https://api.github.com/users/schien/gists{/gist_id}","starred_url":"https://api.github.com/users/schien/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/schien/subscriptions","organizations_url":"https://api.github.com/users/schien/orgs","repos_url":"https://api.github.com/users/schien/repos","events_url":"https://api.github.com/users/schien/events{/privacy}","received_events_url":"https://api.github.com/users/schien/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/w3c/presentation-api/labels/P1","name":"P1","color":"e11d21"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":7,"created_at":"2015-05-25T08:52:42Z","updated_at":"2015-09-01T23:05:29Z","closed_at":null,"body":"Currently we mix the API for controlling page and presenting page in `NavigatorPresentation` and developer will use `navigator.presentation` as the entry point.\r\n\r\nSince we are providing more and more advance feature in this API (see #19), it's cumbersome to provide statement on the usage of each attribute/function.\r\n\r\nTherefore I propose to move all presenting page APIs into a different interface, called `PresentingContext`. The example definition will looks like:\r\n\r\n```\r\ninterface PresentingContext : EventTarget {\r\n  Promise<PresentationSession> getSession();\r\n  Sequence<PresentationSession> getSessions();\r\n  attribute EventHandler onsessionavailable;\r\n};\r\n\r\npartial interface Navigator {\r\n  readonly attibute PresentingContext presentingContext; // null if not presenting page\r\n};\r\n```"},"comment":{"url":"https://api.github.com/repos/w3c/presentation-api/issues/comments/136887900","html_url":"https://github.com/w3c/presentation-api/issues/91#issuecomment-136887900","issue_url":"https://api.github.com/repos/w3c/presentation-api/issues/91","id":136887900,"user":{"login":"mounirlamouri","id":573590,"avatar_url":"https://avatars.githubusercontent.com/u/573590?v=3","gravatar_id":"","url":"https://api.github.com/users/mounirlamouri","html_url":"https://github.com/mounirlamouri","followers_url":"https://api.github.com/users/mounirlamouri/followers","following_url":"https://api.github.com/users/mounirlamouri/following{/other_user}","gists_url":"https://api.github.com/users/mounirlamouri/gists{/gist_id}","starred_url":"https://api.github.com/users/mounirlamouri/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mounirlamouri/subscriptions","organizations_url":"https://api.github.com/users/mounirlamouri/orgs","repos_url":"https://api.github.com/users/mounirlamouri/repos","events_url":"https://api.github.com/users/mounirlamouri/events{/privacy}","received_events_url":"https://api.github.com/users/mounirlamouri/received_events","type":"User","site_admin":false},"created_at":"2015-09-01T23:05:29Z","updated_at":"2015-09-01T23:05:29Z","body":"I think ```PresentingContext``` has multiple downsides:\r\n- ```navigator.presentingContext``` isn't in the ```navigator.presentation``` namespace\r\n- ```PresentingContext``` isn't prefixed with ```Presentation```\r\n- I think ```navigator.presentation.receiver``` is clearer about what it does compared to ```navigator.presentingContext```."}}