W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2010

Application and Chrome

From: Kenneth Rohde Christiansen <kenneth.christiansen@gmail.com>
Date: Mon, 5 Apr 2010 12:02:02 -0300
Message-ID: <h2h484b3831004050802w3b4e1e53k2941f02230e0510f@mail.gmail.com>
To: public-webapps@w3.org
Hi there,

One of the things that I find a bit unclear in
http://dev.w3.org/2006/waf/widgets-vmmf/ , is the use of the Chrome
definition.

The spec says: "Chrome - The chrome comprises the visible parts of the
user agent that do not depend on the content (e.g. tool bars, title
bars, menus).",

but from talking to people, many confuse it with "window decorations"
and "desktop area", because they assume Widgets to be applications and
thus not have chrome, which is what most people do not want as they
strife to make the web apps look like real applications and not
applications running the the browser.

Personally, I think we should leave out the Chrome part from the spec
and talk about window decorations and desktop area instead to make
this 100% clear.

As there is talk about moving the view modes to CSSOM instead,
supporting chrome and none-chrome seems like something that might be
needed instead. One possible solution would be to introduce a new
media feature such as (application) that would turn on application
mode, in contrast to browser mode.

The view-mode has use-cases in the browser case, especially because a
web browser can be windowed/normal, maximized and fullscreen.

On the other hand, the "(view-mode: application)" feels a bit strange
in the browser case, so it might need renaming.

Any comments, input?

-- 
Kenneth Rohde Christiansen
Technical Lead / Senior Software Engineer
Qt Labs Americas, Nokia Technology Institute, INdT
Phone  +55 81 8895 6002 / E-mail kenneth.christiansen at openbossa.org

http://codeposts.blogspot.com ﹆﹆﹆
Received on Monday, 5 April 2010 15:02:55 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:38 GMT