On 15 July 2015 at 10:42, Jonas Sicking <jo...@sicking.cc> wrote: > I also think that "display-mode" and "orientation" (and maybe > "theme_color") properties seem to make much less sense given the > current model of manifests. That seems like information that we'd want > to apply during normal browsing too, which means that it's not really > appropriate for the manifest but rather for a <meta> tag. >
We already have a way for an individual web page to set orientation and theme-color while browsing with page metadata and a JavaScript API. I think the value of having these properties in the manifest is that they can be applied to the URL scope of a whole site rather than just an individual page by applying the manifest to a browsing context to create what the spec calls an "application context", which just means that it already has default metadata applied for a group of web pages. Otherwise you have to wait for each individual page to download to know what display properties to use. This is bad for UX. I don't think the display property is relevant whilst browsing because you are, by definition, in the "browser" display mode. > > I also can't think of a really good use of the "scope" property. I > know it's something we're planning on using in the FirefoxOS pinning > feature, but I'm not convinced that the resulting UI will be > understandable to users. User testing will show. > Yes we are using this for Pin the Web in Firefox OS, and we are putting that UI through user testing, I agree it needs testing. FWIW I think the scope and display properties could be even more important for an implementation in Firefox (on mobile and on desktop), if that was to go ahead. _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
