Re: Proposal to work on Geolocation

2008-05-27 Thread Robert Sayre
; > Noted. I will convey your sentiments to the Team. > > Regards- > -Doug Schepers > W3C Team Contact, SVG, CDF, and WebAPI > > -- Sent from Gmail for mobile | mobile.google.com Robert Sayre "I would have written a shorter letter, but I did not have the time."

Re: Proposed errata for DOM2 Range regarding insertNode()

2008-05-14 Thread Robert Sayre
t also that the intent is clear. Is one of the possible interpretations a real stretch? [1] http://diveintomark.org/archives/2008/05/07/when-the-fall-is-all-thats-left -- Robert Sayre "I would have written a shorter letter, but I did not have the time."

Re: Proposed errata for DOM2 Range regarding insertNode()

2008-05-14 Thread Robert Sayre
On Wed, May 14, 2008 at 8:37 PM, Ian Hickson <[EMAIL PROTECTED]> wrote: > On Wed, 14 May 2008, Robert Sayre wrote: >> >> I'm not sure why you're sending private email about this. I asked a >> simple question on the public list. > > I replied privately t

Re: Proposed errata for DOM2 Range regarding insertNode()

2008-05-14 Thread Robert Sayre
hat have been written down for at least 5 years or something like that. confused, Rob -- Robert Sayre "I would have written a shorter letter, but I did not have the time."

Re: [selectors-api] Why no querySelector(All) on DocumentFragments?

2008-03-13 Thread Robert Sayre
Lachlan. :-) Fully disagree. -- Robert Sayre "I would have written a shorter letter, but I did not have the time."

Re: Geolocation API proposal

2008-03-07 Thread Robert Sayre
On Thu, Mar 6, 2008 at 5:55 PM, Aaron Boodman <[EMAIL PROTECTED]> wrote: > > I posted this to the WhatWG mailing list, but it was suggested that this > might be a more appropriate place. Surely WhatWG would be more convenient? I mean, the editor can just rubber stamp it for you.

Re: multipart, server-sent events, and

2008-02-19 Thread Robert Sayre
On Feb 19, 2008 2:30 PM, Maciej Stachowiak <[EMAIL PROTECTED]> wrote: > > On Feb 19, 2008, at 11:12 AM, Robert Sayre wrote: > > > On Feb 19, 2008 1:50 PM, Maciej Stachowiak <[EMAIL PROTECTED]> wrote: > >> > >> Probably the appropriate forum to make t

Re: multipart, server-sent events, and

2008-02-19 Thread Robert Sayre
ching> FWIW, the next Firefox beta will have pipelining enabled for https. I won't be surprised if we hit bad bugs. Falling back to https in combination with your proposed connection token might be a fine idea. -- Robert Sayre "I would have written a shorter letter, but I did not have the time."

Re: multipart, server-sent events, and

2008-02-18 Thread Robert Sayre
On Feb 19, 2008 12:20 AM, Mark Baker <[EMAIL PROTECTED]> wrote: > > Well, I'd like to see some hard evidence of this before we write it off. I'd like to see Maciej go first. ;) -- Robert Sayre "I would have written a shorter letter, but I did not have the time."

Re: XHR: definition of same-origin

2007-08-28 Thread Robert Sayre
> > > In particular, we would not consider https://example.com:443/ to be > the same origin as https://example.com/. Agree. This should come in handy: - RFC 3986, section 6.2.3 (Scheme-Based Normalization) -- Robert Sayre "I would have written a shorter letter, but I did not have the time."

Re: [xhr2] PATCH support

2007-08-06 Thread Robert Sayre
On 8/6/07, Anne van Kesteren <[EMAIL PROTECTED]> wrote: > On Mon, 06 Aug 2007 15:38:52 +0200, Robert Sayre <[EMAIL PROTECTED]> wrote: > > Partial resource updates are a pretty compelling use case for XHR2. > > You can always use POST for this, but it's a pain

[xhr2] PATCH support

2007-08-06 Thread Robert Sayre
Partial resource updates are a pretty compelling use case for XHR2. You can always use POST for this, but it's a pain if you need to use POST for something else. -- Robert Sayre "I would have written a shorter letter, but I did not have the time."

Re: [XMLHttpRequest] update from the editor

2007-05-14 Thread Robert Sayre
oo strongly about this issue. -- Robert Sayre

Re: [XMLHttpRequest] update from the editor

2007-05-14 Thread Robert Sayre
water under the bridge, so I personally feel that the IETF should register and document it. The registration procedures are a lot easier now. -- Robert Sayre "I would have written a shorter letter, but I did not have the time."

Re: XMLHttpRequest for Last Call

2007-02-17 Thread Robert Sayre
On 2/17/07, Anne van Kesteren <[EMAIL PROTECTED]> wrote: On Sat, 17 Feb 2007 21:15:04 +0100, Robert Sayre <[EMAIL PROTECTED]> wrote: > Where do the requirements for the username and password productions > come from? Is there an old list discussion on them? Mainly offlist feed

Re: XMLHttpRequest for Last Call

2007-02-17 Thread Robert Sayre
do the requirements for the username and password productions come from? Is there an old list discussion on them? -- Robert Sayre

Re: Selectors API: Multiple elements with the same ID

2007-01-27 Thread Robert Sayre
p/author/dhtml/reference/methods/getelementbyid.asp> -- Robert Sayre

Re: Progress event spec

2007-01-27 Thread Robert Sayre
On 1/27/07, Jim Ley <[EMAIL PROTECTED]> wrote: The arbritrariness of the value is why I do not feel it should be in the spec, but left to vendors. I'd be interested to hear from browser vendors that want to change or delete the values in Hixie's proposal. -- Robert Sayre

Re: Progress event spec

2007-01-27 Thread Robert Sayre
On 1/27/07, Jim Ley <[EMAIL PROTECTED]> wrote: So why is the value 10ms chosen? 10ms is already used for other things. <http://lxr.mozilla.org/seamonkey/source/dom/src/base/nsGlobalWindow.cpp#206> <https://bugzilla.mozilla.org/show_bug.cgi?id=123273> -- Robert Sayre

Re: Progress event spec

2007-01-27 Thread Robert Sayre
elieve they should. Mozilla receives bug reports when we fail to match IE's event timing for XHR. -- Robert Sayre

Re: Selectors API naming

2007-01-26 Thread Robert Sayre
t of conditions. You should take them up with the right part of W3C if you want to have an effective conversation. If you want to create effective specifications, the way to respond to harsh technical and ethical criticism is not to dismiss it by pointing out that you are following the correct bureaucratic procedure. -- Robert Sayre

Re: Selectors API naming

2007-01-26 Thread Robert Sayre
ammers, and Semantic Web advocates. -- Robert Sayre "I would have written a shorter letter, but I did not have the time."

Re: Selectors API naming

2007-01-26 Thread Robert Sayre
On 1/26/07, Charles McCathieNevile <[EMAIL PROTECTED]> wrote: On Fri, 26 Jan 2007 13:05:13 -0500, Robert Sayre <[EMAIL PROTECTED]> wrote: Roughly speaking, the rationale was that nobody except Anne felt get was good, there was little support for match and strong resistance, and

Re: Selectors API naming

2007-01-26 Thread Robert Sayre
On 1/26/07, Robin Berjon <[EMAIL PROTECTED]> wrote: On Jan 25, 2007, at 21:51, Robert Sayre wrote: > I encourage you to read the WG charter. > <http://www.w3.org/2006/webapi/admin/charter> I think Jon knows the charter :) Well, I thought I would match his tone :) &

Re: Selectors API naming

2007-01-25 Thread Robert Sayre
rwise respond to public comments from WG members and the general public, I think it should change its charter to be entirely Member Confidential. I wouldn't want that, but it seems like it would be more accurate. -- Robert Sayre

Re: Selectors API updates

2007-01-10 Thread Robert Sayre
On 1/9/07, Anne van Kesteren <[EMAIL PROTECTED]> wrote: These names are short, don't clash with autocomplete and provide a superset of the functionality given by the other get* methods. Works for me. Thanks, Anne. -- Robert Sayre <http://franklinmint.fm> <http://mozilla.com>

Re: Selectors API naming

2006-12-20 Thread Robert Sayre
uffy+bunnies+eat+grass", but couldn't find any relevant information on the topic there either, oddly enough. Thanks for that. -- Robert Sayre

Re: Selectors API naming

2006-12-20 Thread Robert Sayre
ly in that regard. HA! Amen to that. Well, well. Common ground. :) -- Robert Sayre

Re: Selectors API naming

2006-12-20 Thread Robert Sayre
re for. To become a Recommendation, it has to go through a lot more analysis by multiple parties and multiple implementations, etc Recommendations seem to vary widely in that regard. -- Robert Sayre

Re: Selectors API naming

2006-12-20 Thread Robert Sayre
hen each of the methods takes a string mini-language as an argument. Ian Hickson wrote: In my experience with cat fighting on mailing lists, what you'll end up having is whoever gave up last wins. This is more a test of who has the most free time, not a test of who has the strongest case. Agree. good luck, Robert Sayre

Re: Selectors API naming

2006-12-20 Thread Robert Sayre
implement the "Quick DOM" standard could be catered to by adding a script element. -- Robert Sayre "I would have written a shorter letter, but I did not have the time."

Re: Selectors API naming

2006-12-20 Thread Robert Sayre
t requires JavaScript programmers to type 22 characters before encountering characters that uniquely identify it, and 19 characters before it's clear that the method will return a NodeList. The JS library authors of the world seem to understand this argument. If XPath can use "evaluate"[1]

Re: Selectors API naming

2006-12-20 Thread Robert Sayre
that's the nice thing about getElementsBySelector. It's like picking 6 names all at once. :) -- Robert Sayre

Re: Selectors API naming

2006-12-20 Thread Robert Sayre
ntById. The names in the draft look fine to me. I like my fingers, and I don't like autocomplete :) -- Robert Sayre