Hi,
I know that not many people on this list care about the WebSQLDatabase spec
anymore (especially when it comes to changing it), but Chromium extension
developers do. So I was hoping somebody could explain the idea behind having
openDatabase() take a creationCallback. As I understand it, the cal
2010/2/23 Jonas Sicking
>
> The same is not true for the suggest notification API. Several
> proposals have been put forward that do not rely on fallback.
>
>
One of the reasons I stepped back from this discussion is because it seemed
clear that we weren't going to make progress on solutions unti
This was recently brought to my attention by one of the web app developers
in my office:
http://dev.w3.org/2006/webapi/FileAPI/#lifetime
User agents MUST ensure that the lifetime of File URN <#dfn-fileURN>s is the
same as the lifetime of the Document [HTML5 <#HTML5>] of the origin script
which sp
Am 23. Februar 2010 13:44 schrieb Jonas Sicking :
> 2010/2/23 Ian Fette (イアンフェッティ) :
> > Am 23. Februar 2010 12:11 schrieb Anne van Kesteren :
> >>
> >> On Tue, 23 Feb 2010 20:20:13 +0100, Ian Fette (イアンフェッティ)
> >> wrote:
> >>>
> >>> CreateInteractiveNotification(in DOMString text-fallback, [Opti
2010/2/23 Ian Fette (イアンフェッティ) :
> Am 23. Februar 2010 12:11 schrieb Anne van Kesteren :
>>
>> On Tue, 23 Feb 2010 20:20:13 +0100, Ian Fette (イアンフェッティ)
>> wrote:
>>>
>>> CreateInteractiveNotification(in DOMString text-fallback, [Optional] in
>>> DOMString MimeType1, [Optional] in DOMString Notific
2010/2/23 Ian Fette (イアンフェッティ)
> Am 23. Februar 2010 12:11 schrieb Anne van Kesteren :
>
> On Tue, 23 Feb 2010 20:20:13 +0100, Ian Fette (イアンフェッティ) <
>> ife...@google.com> wrote:
>>
>>> CreateInteractiveNotification(in DOMString text-fallback, [Optional] in
>>> DOMString MimeType1, [Optional] in
Doug Schepers wrote (on 2/23/10 2:43 PM):
HTML is a little bit more widely adopted than
SVG (I suspect that there are 10x as many HTML documents as SVG
documents on the Web).
I've been told offlist that it may not be obvious that I was joking
here... "10x" is an absurdly low figure... HTML is
Am 23. Februar 2010 12:11 schrieb Anne van Kesteren :
> On Tue, 23 Feb 2010 20:20:13 +0100, Ian Fette (イアンフェッティ) <
> ife...@google.com> wrote:
>
>> CreateInteractiveNotification(in DOMString text-fallback, [Optional] in
>> DOMString MimeType1, [Optional] in DOMString NotificationFormat1,
>> [Optio
On Tue, 23 Feb 2010 20:20:13 +0100, Ian Fette (イアンフェッティ)
wrote:
CreateInteractiveNotification(in DOMString text-fallback, [Optional] in
DOMString MimeType1, [Optional] in DOMString NotificationFormat1,
[Optional]
in DOMString MimeType2, [Optional] NotificationFormat2, ...)
forgive my broken
Hi, Ian-
No need to apologize... HTML is a little bit more widely adopted than
SVG (I suspect that there are 10x as many HTML documents as SVG
documents on the Web).
It may be that only specifying text and HTML notifications is the best
way forward for now, I just wanted to make sure it was
Doug -
I did not mean to be HTML centric, apologies. I'm currently going through a
debate in my mind (scary thing) about whether allowing an arbitrary mime
type and content would be good or bad. My gut sense here is that if the UA
is capable of displaying it, we should allow it, and it will be use
Replied offline...
Cheers
On Tue, 23 Feb 2010 19:28:46 +0100, David Geer wrote:
Can someone point me to documentation on what is being developed in this
Working Group in the way of web services that specifically serve the
needs of Rich Internet Applications? I am a technology reporter cove
This seems like a balance and all around reasonable way to move forward.
2010/2/23 Ian Fette (イアンフェッティ)
> This thread seems to have languished, and I'm trying to figure out how to
> move forward here.
>
> My understanding, grossly simplified, of the current state of the world is
> this:
>
> 1. S
Can someone point me to documentation on what is being developed in this
Working Group in the way of web services that specifically serve the needs of
Rich Internet Applications? I am a technology reporter covering RIAs. Links
would be great.
Best Regards,
David Geer
440-964-9832
http://www.lin
Hi, Ian-
I generally agree with you, and certainly with your sentiment. Not to
go all SVG on you, but why "*HTMLNotification"? I understand that HTML
is really common, and that increasingly SVG can be used as part of HTML,
but there are lots of devices out there (TVs, mobiles, set-top boxes)
This thread seems to have languished, and I'm trying to figure out how to
move forward here.
My understanding, grossly simplified, of the current state of the world is
this:
1. Some people have a desire to show HTML / interactive notifications, to
support use cases like "remind me of this calenda
On 23.02.2010 13:53, Hans Meiser wrote:
I should have been more precise in my last reply:
However, I see a lack in this definition
(http://tools.ietf.org/html/rfc2616#section-9.4) regarding resources
usually obtained by a POST request:
If uploaded data is not going to be sent to the host along
I should have been more precise in my last reply:
However, I see a lack in this definition
(http://tools.ietf.org/html/rfc2616#section-9.4) regarding resources usually
obtained by a
POST request:
If
uploaded data is not going to be sent to the host along with a HEAD request,
not ALL headers
OK, I see... Given this definition then, the case is closed.
However, I see a lack in the definition regarding resources obtained by a POST
request: Not ALL headers will be returned with expected values if uploaded data
is not going to be sent to the host.
Best regards,
www.axeldahmen.de
Axel
On Tue, 23 Feb 2010 12:29:59 +0100, Hans Meiser
wrote:
I believe this spec ought to be updated to also exclude POST data from
being uploaded for HTTP request methods like DELETE, TRACE, OPTIONS.
As I said in the bug, we do not want to constrain HTTP more than we
already do.
I believe this i
Hi Anne,
> > I believe this spec ought to be updated to also exclude POST data from
> > being uploaded for HTTP request methods like DELETE, TRACE, OPTIONS.
>
> As I said in the bug, we do not want to constrain HTTP more than we
> already do.
I believe this is not a question of wanting but a q
On Tue, 23 Feb 2010 11:06:20 +0100, Hans Meiser
wrote:
I believe this spec ought to be updated to also exclude POST data from
being uploaded for HTTP request methods like DELETE, TRACE, OPTIONS.
As I said in the bug, we do not want to constrain HTTP more than we
already do.
Plus, I beli
Hello,
I noticed that the Mozilla XMLHttpRequest send() method implementation uploads
POST data on any protocol other than GET. According to a discussion at
Bugzilla, this is due to the specs:
http://www.w3.org/TR/XMLHttpRequest/#the-send-method
I believe this spec ought to be updated to also
23 matches
Mail list logo
