+1 to a non-bool It should be on window rather then on navigator since navigator has scope of the whole browser app, while windows may be in different modes. Could be window.displayMode which returns strings "normal" or "application". "if(window.displayMode)" would be a test for the feature.
Or should it be something like window.chromiumDisplayMode to avoid conflict with future standard? On Tue, Jan 13, 2009 at 8:38 AM, Glen Murphy <g...@chromium.org> wrote: > > >> 3) Expose a boolean readonly property to the dom (say the Window > >> object) where a user can query whether or not they are in app mode > >> ( either Window.Application mode or possible Window.AddressBar ) > >> > >> We would like to do (3). Is this possible? > > > > I think 3 is fine, but I'm not really someone who should be approving > such > > changes. > > Other browsers have added properties to window.navigator to signal > > application state (see Firefox and > > navigator.onLine: > https://developer.mozilla.org/en/DOM/window.navigator.onLine). > > With window.fullScreen, there's precedent for properties indicating > display modes. Not sure if it should be a single bool though, as there > might be a disconnect between checking for display mode and behavior - > for example, what happens if we add other display modes like tabbed > application or gadget; these may have other link opening behaviors. > > > > --~--~---------~--~----~------------~-------~--~----~ Chromium Developers mailing list: chromium-dev@googlegroups.com View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-dev -~----------~----~----~----~------~----~------~--~---
