Re: New manifest spec - ready for FPWD?

On Tue, 03 Dec 2013 19:27:15 +0100, Jonas Sicking <jonas@sicking.cc> wrote:

> On Mon, Dec 2, 2013 at 9:40 PM, Marcos Caceres <w3c@marcosc.com> wrote:
>>> What I think we should have is something like:
>>>
>>> "chrome": {
>>> "back": true
>>> }
>>
>> Yep, this is currently captured here:
>> https://github.com/w3c/manifest/issues/76
>>
>> Those of us working on this still need to investigate FxOS a bit more  
>> to see what people are using in practice and why (e.g., how much  
>> granularity do we really need? to the button level “forward”/“back", or  
>> can we just say “navigation-bar”, etc.). Captured here:
>> https://github.com/w3c-webmob/installable-webapps/issues/17
>
> Simply wanting *just* the back/forward buttons has been common. I
> could imagine apps relying on the "reload" button as well.

Yes. Especially for things that come off the web (as opposed to packaged  
apps).

> I have not heard of, but I could imagine, apps wanting to rely in the
> title of the page being displayed.

Quite possibly
[use case snipped]
>
> The "url bar" is a very common separate UI piece on most platforms.
> However it's unclear how a URL bar would work in a standalone UI.
> Would the user be able to type any URL while still remaining in within
> the standalone UI? Seems surprising if we imagine that the standalone
> UI uses the icon of the app. Though we could always open any typed URL
> in the default browser. Anyway, staying away from url-bar seems safer
> for now.

Yes. In-apge Search is something that might also be useful within an app -  
especially if you can find out it is happening and respond to it  
intelligently if the app hides things by default.

> Beyond that I think platforms diverge a lot. In FirefoxOS we're
> planning on adding a whole menu which contains things like "bookmark",
> "save", "share", "reading list" etc.

Hmm. I don't think platforms diverge that widely, but I agree that we  
should expect different platforms to offer different functions. We  
probably want to agree on what we call anything, rather than have  
different names for each different browser (кладки is intuitive to most  
people who will develop for Yandex, but might not be the best choice  
overall ;) ).

cheers

Chaals

-- 
Charles McCathie Nevile - Consultant (web standards) CTO Office, Yandex
       chaals@yandex-team.ru         Find more at http://yandex.com

Received on Tuesday, 3 December 2013 21:44:28 UTC