Re: [whatwg] Proposed additions to ClientInformation interface

2009-02-11 Thread Ian Hickson
On Sat, 17 Jan 2009, Mark Finkle wrote: > On Mon, Jul 21, 2008 at 10:10 PM, Ian Hickson wrote: > > On Mon, 7 Jul 2008, Mark Finkle wrote: > > > > > > The only reason I can see for such an API is to get the user's > > > permission to use features that _may_ be a bit of a security risk to > > > no

Re: [whatwg] Proposed additions to ClientInformation interface

2009-01-16 Thread Mark Finkle
On Mon, Jul 21, 2008 at 10:10 PM, Ian Hickson wrote: On Mon, 7 Jul 2008, Mark Finkle wrote: > > > > The only reason I can see for such an API is to get the user's > > permission to use features that _may_ be a bit of a security risk to > > normal webapps. Clipboard, dock badging, local file drag-

Re: [whatwg] Proposed additions to ClientInformation interface

2009-01-16 Thread Ian Hickson
On Tue, 8 Jul 2008, Maciej Stachowiak wrote: > > I think there are two competing ideas here that are sometimes in > tension: > > A) Web applications are just Web pages and should be indistinguishable > from any other Web page. > > B) Web applications are just applications and should be > indis

Re: [whatwg] Proposed additions to ClientInformation interface

2008-07-21 Thread Ian Hickson
Based on discussions around this topic I've drafted a very experimental section introducing a element. The element is expected to be styled much like an element by user agents: bb:enabled { color: blue; text-decoration: underline; } bb:disabled { display: none; } bb[type=makeapp]:e

Re: [whatwg] Proposed additions to ClientInformation interface

2008-07-14 Thread Křištof Želechovski
@lists.whatwg.org; Ian Hickson; Brady Eidson; [EMAIL PROTECTED] Subject: Re: [whatwg] Proposed additions to ClientInformation interface On Tue, Jul 8, 2008 at 1:01 PM, Krzysztof Żelechowski <[EMAIL PROTECTED]> wrote: Tuesday 08 of July 2008 05:10:46 Mark Finkle napisał(a): > On M

Re: [whatwg] Proposed additions to ClientInformation interface

2008-07-09 Thread Ian Hickson
I'll reply to this in more detail in due course, but I'm still interested in the idea, and would like to discuss that further: On Tue, 8 Jul 2008, Maciej Stachowiak wrote: > > > > One possibility for addressing these requirements would be an element > > that acts as a link, button, or icon, o

Re: [whatwg] Proposed additions to ClientInformation interface

2008-07-08 Thread Mark Finkle
On Tue, Jul 8, 2008 at 1:01 PM, Krzysztof Żelechowski <[EMAIL PROTECTED]> wrote: > Tuesday 08 of July 2008 05:10:46 Mark Finkle napisał(a): > > On Mon, Jul 7, 2008 at 6:04 PM, Ian Hickson <[EMAIL PROTECTED]> wrote: > > > On Fri, 27 Jun 2008, Brady Eidson wrote: > > > * Sites want to offer a way f

Re: [whatwg] Proposed additions to ClientInformation interface

2008-07-08 Thread Krzysztof Żelechowski
Tuesday 08 of July 2008 05:10:46 Mark Finkle napisał(a): > On Mon, Jul 7, 2008 at 6:04 PM, Ian Hickson <[EMAIL PROTECTED]> wrote: > > On Fri, 27 Jun 2008, Brady Eidson wrote: > > * Sites want to offer a way for users to opt into a standalone mode > > ("can we offer a link to download one of thes

Re: [whatwg] Proposed additions to ClientInformation interface

2008-07-08 Thread Krzysztof Żelechowski
Tuesday 08 of July 2008 14:45:23 Maciej Stachowiak napisał(a): > The way I think of standalone(*) Web applications is that they should   > work well in the browser context, but be able to provide progressive   > enhancement when in standalone mode. For example, native applications   > have custom i

Re: [whatwg] Proposed additions to ClientInformation interface

2008-07-08 Thread Maciej Stachowiak
On Jul 7, 2008, at 3:04 PM, Ian Hickson wrote: Actually there are a number of features that cater for this use case already, like the sizes="" attribute on rel=icon, and one of the names. In general, though, the idea is to make these kinds of applications as indistinguishable from other Web

Re: [whatwg] Proposed additions to ClientInformation interface

2008-07-07 Thread Mark Finkle
On Mon, Jul 7, 2008 at 6:04 PM, Ian Hickson <[EMAIL PROTECTED]> wrote: > On Fri, 27 Jun 2008, Brady Eidson wrote: > > > > There is one aspect to this notion of "Web Applications" that is being > > explored by multiple vendors but hasn't been explicitly addressed in > > HTML5 quite yet: the "stand

Re: [whatwg] Proposed additions to ClientInformation interface

2008-07-07 Thread Aaron Boodman
On Fri, Jun 27, 2008 at 2:04 PM, Brady Eidson <[EMAIL PROTECTED]> wrote: > Second: "void makeStandalone();" I think one disadvantage of this approach is that it can only be called in response to a user action if you want to avoid it being used to annoy or spam. It's unfortunate to have an API tha

Re: [whatwg] Proposed additions to ClientInformation interface

2008-07-07 Thread Robert O'Callahan
On Tue, Jul 8, 2008 at 11:06 AM, Ian Hickson <[EMAIL PROTECTED]> wrote: > Indeed. (This isn't unique to this proposal; the original idea of an API > would be even more vulnerable to this, since scripts could just invoke it > at any time they please.) > Of course, but that can be seen as an advant

Re: [whatwg] Proposed additions to ClientInformation interface

2008-07-07 Thread Ian Hickson
On Tue, 8 Jul 2008, Robert O'Callahan wrote: > On Tue, Jul 8, 2008 at 10:04 AM, Ian Hickson <[EMAIL PROTECTED]> wrote: > > > > One possibility for addressing these requirements would be an element > > that acts as a link, button, or icon, or some such, and which invokes > > user agent features. S

Re: [whatwg] Proposed additions to ClientInformation interface

2008-07-07 Thread Robert O'Callahan
On Tue, Jul 8, 2008 at 10:04 AM, Ian Hickson <[EMAIL PROTECTED]> wrote: > One possibility for addressing these requirements would be an element that > acts as a link, button, or icon, or some such, and which invokes user > agent features. Something like: > > > It's an interesting idea. You'd h

Re: [whatwg] Proposed additions to ClientInformation interface

2008-07-07 Thread Ian Hickson
On Fri, 27 Jun 2008, Brady Eidson wrote: > > There is one aspect to this notion of "Web Applications" that is being > explored by multiple vendors but hasn't been explicitly addressed in > HTML5 quite yet: the "stand alone web application." Actually there are a number of features that cater for