c...@opera.com]
Sent: Tuesday, August 10, 2010 12:30 AM
To: gaut...@opera.com; SULLIVAN, BRYAN L (ATTCINW)
Cc: Web Applications Working Group WG
Subject: Re: ACTION-568: Create an alternative mechanism for openURL andsend it
to the mail list (Web Applications Working Group)
On 8/10/10
urposes it is supported.
Thanks for the clarification.
Thanks,
Bryan Sullivan | AT&T
-Original Message-
From: Anne van Kesteren [mailto:ann...@opera.com]
Sent: Monday, August 09, 2010 9:51 PM
To: Jonas Sicking; SULLIVAN, BRYAN L (ATTCINW)
Cc: WebApps WG
Subject: Re: [XHR] Status
document.getElementById("text").innerHTML = "loadFile: "
+ url + "File should appear below";
extref.setAttribute('src', encurl);
}
}
Thanks,
Bryan Sullivan | AT&T
-Original Message-
From: Jonas
van Kesteren [mailto:ann...@opera.com]
Sent: Monday, August 09, 2010 2:49 PM
To: Jonas Sicking; SULLIVAN, BRYAN L (ATTCINW)
Cc: WebApps WG
Subject: Re: [XHR] Status Update
On Mon, 09 Aug 2010 23:37:25 +0200, SULLIVAN, BRYAN L (ATTCINW)
wrote:
> Are you saying that it should not be possible no
---
From: marc...@opera.com [mailto:marc...@opera.com]
Sent: Monday, August 09, 2010 2:51 PM
To: SULLIVAN, BRYAN L (ATTCINW)
Cc: Web Applications Working Group WG
Subject: RE: ACTION-568: Create an alternative mechanism for openURL andsend it
to the mail list (Web Applications Working Group)
Quoting
Anne,
Are you saying that it should not be possible now (with XHR L1) to
receive HTML files via XHR ("Receiving HTML documents would indeed be a
newish feature ") ?
This does actually work for me in XHR L1, so I'm unclear about what you
mean below.
Thanks,
Bryan Sullivan | AT&T
-Original
Marcos,
That method works for well-know URI schemes except for http:// and https://.
The openURL() method would have launched the browser for those schemes, and we
still need a method to do that.
I was not able to attend the last week's call and was not aware there was a
plan to remove the ope
ivan | AT&T
-Original Message-
From: Eric Uhrhane [mailto:er...@google.com]
Sent: Wednesday, June 16, 2010 4:42 PM
To: SULLIVAN, BRYAN L (ATTCINW)
Cc: a...@mozilla.com; Robin Berjon; public-device-a...@w3.org; Ian
Fette; Web Applications Working Group WG
Subject: Re: Transferring File* t
ryFilesystem are quite useful also, and may support the
majority of use cases anyway.
Thanks,
Bryan Sullivan | AT&T
From: Mike Clement [mailto:mi...@google.com]
Sent: Tuesday, June 15, 2010 4:40 PM
To: SULLIVAN, BRYAN L (ATTCINW)
Cc: a...@mozilla.com; Robin Berjon; public-device-a...@w
T
From: Mike Clement [mailto:mi...@google.com]
Sent: Tuesday, June 15, 2010 3:42 PM
To: SULLIVAN, BRYAN L (ATTCINW)
Cc: a...@mozilla.com; Robin Berjon; public-device-a...@w3.org; Ian
Fette; Web Applications Working Group WG
Subject: Re: Transferring File* to WebApps - redux
Hi,
Am I corre
ly secure models for Web application access to device resources
will be defined as APIs.
Thanks,
Bryan Sullivan | AT&T
-Original Message-
From: Arun Ranganathan [mailto:a...@mozilla.com]
Sent: Tuesday, June 15, 2010 2:53 PM
To: SULLIVAN, BRYAN L (ATTCINW)
Cc: Robin Berjon; public-d
cking.cc]
Sent: Tuesday, June 15, 2010 2:48 PM
To: SULLIVAN, BRYAN L (ATTCINW)
Cc: a...@mozilla.com; Robin Berjon; public-device-a...@w3.org; Ian
Fette; Web Applications Working Group WG
Subject: Re: Transferring File* to WebApps - redux
On Tue, Jun 15, 2010 at 2:24 PM, SULLIVAN, BRYAN L (ATTCINW
options to the user-centric/control
paradigms of the past.
Thanks,
Bryan Sullivan | AT&T
-Original Message-
From: Arun Ranganathan [mailto:a...@mozilla.com]
Sent: Tuesday, June 15, 2010 1:48 PM
To: SULLIVAN, BRYAN L (ATTCINW)
Cc: Robin Berjon; public-device-a...@w3.org; Ian Fett
I will not be able to attend today's call.
Bryan | AT&T
Hi all,
This is a question for both the Webapps Widgets and Web API followers.
In testing widget engine rendering of plain text files as the source of
an iframe, I came across a problem I need your input on. It appears that
when a widget retrieves a file from the widget package using XHR *OR* as
n Sullivan | AT&T
-Original Message-
From: Charles Pritchard [mailto:ch...@jumis.com]
Sent: Thursday, March 04, 2010 10:31 AM
To: SULLIVAN, BRYAN L (ATTCINW)
Cc: Doug Schepers; public-webapps@w3.org
Subject: Re: Event handlers - Pointer Devices
`
> On the main (or more useful) poin
hed to it.
I'd like to see some clearer distinction between the charters on these points.
Thanks,
Bryan Sullivan | AT&T
-Original Message-
From: Doug Schepers [mailto:schep...@w3.org]
Sent: Thursday, March 04, 2010 7:08 AM
To: SULLIVAN, BRYAN L (ATTCINW)
Cc: Charles Pritchard;
This might be better discussed by the DAP group, as it's clearly a
"device API" topic.
Also it would be interesting to hear from Apple and Wacom (without
unnecessary details at this point), what areas of touch interface
capabilities would be problematic for W3C to create API's for, from an
IPR per
p;T
-Original Message-
From: Ian Hickson [mailto:i...@hixie.ch]
Sent: Monday, November 30, 2009 6:52 PM
To: SULLIVAN, BRYAN L (ATTCINW)
Cc: WebApps WG
Subject: Re: [EventSource] Comments to the current draft
On Tue, 27 Oct 2009, SULLIVAN, BRYAN L (ATTCINW) wrote:
>
> Re "T
Maciej,
Security is important in DAP, and should be considered carefully in the context
of each API and its use cases. There is no "one size fits all" solution to
security, and that includes approaches based solely upon explicit user action
(including explicitly expressed permission via dialog
:ro...@berjon.com]
Sent: Wednesday, November 18, 2009 4:00 AM
To: SULLIVAN, BRYAN L (ATTCINW)
Cc: Marcos Caceres; WebApps WG
Subject: Re: [WARP] Comments to WARP spec
On Nov 9, 2009, at 20:22 , SULLIVAN, BRYAN L (ATTCINW) wrote:
> (1) we need to be specific about which API's / resource types
009 3:57 AM
To: Marcin Hanclik
Cc: Marcos Caceres; SULLIVAN, BRYAN L (ATTCINW); WebApps WG
Subject: Re: [WARP] Comments to WARP spec
On Nov 12, 2009, at 16:36 , Marcin Hanclik wrote:
> I understand that too many details may not work or be an obstacle in the
> adoption.
> However, I derive
Test 2: If the widget engine does not allow external image
references, no image will
be shown below:
http://dev.opera.com/img/logo-beta.gif"/>
Best regards,
Bryan Sullivan | AT&T
-Original Message-
From: Marcos Caceres [mailto:marc..
mailto:marc...@opera.com]
Sent: Tuesday, November 10, 2009 7:30 AM
To: SULLIVAN, BRYAN L (ATTCINW)
Cc: WebApps WG
Subject: Re: [WARP] Comments to WARP spec
SULLIVAN, BRYAN L (ATTCINW) wrote:
> Marcos,
> I agree there is an assumption behind the approach I proposed, which I also
> b
b security model, so we need
to fix the element definition somehow.
Best regards,
Bryan Sullivan | AT&T
-Original Message-
From: Marcos Caceres [mailto:marc...@opera.com]
Sent: Tuesday, November 10, 2009 1:36 AM
To: SULLIVAN, BRYAN L (ATTCINW)
Cc: WebApps WG
Subject: Re: [WAR
o indicate which types of references
should be allowed for the domain
My preference would be (1), but I proposed the use of "tag=" to illustrate how
(2) might work.
Best regards,
Bryan Sullivan | AT&T
-Original Message-
From: Marcos Caceres [mailto:marc...@opera.com]
Se
Here are the comments I had to the WARP spec in the Webapps/DAP joint
meeting:
1) Does "*" grant/require either HTTP or HTTPS as schemes? It would be
better to allow "https://*/"; or "http://*/"; distinctly since some
applications may not be allowed by policy to access specific sources
using non-s
Hi all,
Here are some comments / questions for clarification re the current
Server Sent Events draft
(http://www.w3.org/TR/2009/WD-eventsource-20091029/). If there is time
next week, and these points are not addressed by email before then, I
would appreciate the opportunity to have a F2F discussio
Hi Charles,
I have an agenda item for the AOB section or wherever it can fit. I will be
spending most of the time with DAP and part with Webapps (Widgets), but will
try to balance the agendas to be in the APIs meeting as much as possible.
The basic question I have is what is the relationship of
Regrets, I have a conflicting meeting.
Best regards,
Bryan Sullivan | AT&T
Hi Art,
My action http://www.w3.org/2008/webapps/track/actions/357 can be closed. The
table that was requested was provided in Widgets 1.0: Window Modes and Media
Query Extensions http://dev.w3.org/2006/waf/widgets-wm/Overview.src.html. I
didn't do it, but it does meet the original request relat
Title: Questions on A&E spec
Here are a couple of potentially easy questions on the Widgets 1.0: APIs and Events spec:
5.15 The openURL() Method
Does "the appropriate protocol handler" mean an external application (e.g. browser for http://) is invoked, or can the "handler" be the widget u
Title: Response to ACTION-348
Here is my input re my action for use cases to the WARP spec (http://www.w3.org/2008/webapps/track/actions/348)
Use cases for WARP spec related to the following access element attributes (add two new attributes):
required: Optional.
- A boolean attribut
33 matches
Mail list logo
