On Thu, 20 Jan 2011 11:51:17 +0100, Charles McCathieNevile
cha...@opera.com wrote:
Use cases
* An app can provide notifications (using the Web Notification stuff
that is under developemnt) when it is not visible/focused, but skip them
when it is to minimise distractions and reduce
On Jan 20, 2011, at 22:10 , Marcos Caceres wrote:
On 1/20/11 6:48 PM, Arthur Barstow wrote:
If people have spare time for the widgets specs, it seems like that
time would be better spent moving the existing specs forward.
Agree. Just testing the waters to see if any other members were
On 1/21/11 11:48 AM, Robin Berjon wrote:
On Jan 19, 2011, at 19:39 , Marcos Caceres wrote:
On 1/17/11 1:56 PM, Robin Berjon wrote:
Nothing in P+C is super-hard to implement, but the l12n parts
account for most of the complexity,
I've only implemented the i18n stuff in Javascript, but I
note that you don't *need* to duplicate html files.
the format allows for one to have json based localizations.
a nokia maps application uses json for localization and could be
easily ported to the widget format.
i can't do it publicly because i don't own/manage the code.
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11834
Summary: API for send/receive of binary data? Current IETF
protocol drafts have binary type. Consider typed
arrays (ArrayBuffer).
Product: WebAppsWG
Version: unspecified
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11835
Summary: Please do *not* require a same-origin restriction in
user agents (as currently specified under Security
Considerations)! This cross-origin data leakage
security
On Fri, 21 Jan 2011 19:32:57 +0100, timeless timel...@gmail.com wrote:
note that you don't *need* to duplicate html files.
the format allows for one to have json based localizations.
a nokia maps application uses json for localization and could be
easily ported to the widget format.
Could
On Thu, Jan 20, 2011 at 12:50 PM, Glenn Maynard gl...@zewt.org wrote:
On Thu, Jan 20, 2011 at 2:36 PM, Alex Komoroske komoro...@chromium.orgwrote:
If you intend preview to include large but smaller-than-full-size
previews, eg. scaled to 50%, I'd recommend avoiding the word thumbnail; I
think
The Entry.toURI method specified in the FileSystem spec [1] currently
has an open issue to define its format. I believe we also need to
describe the ways in which it can and cannot be used, as some
potential uses may have security implications.
I propose the following format:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=11836
Summary: Don't specify the transport, just specify API and
protocol
Product: WebAppsWG
Version: unspecified
Platform: PC
OS/Version: All
Status: NEW
On Fri, Jan 21, 2011 at 6:12 PM, Eric Uhrhane er...@google.com wrote:
I think that, for the domain that owns the asset referred to by the
URI, pretty much any reasonable use should be allowed:
video/audio/img/iframe/script sources, XHR [GET only], etc. I'm
iffier on allowing any access to
11 matches
Mail list logo
