On Thu, Dec 8, 2011 at 2:36 PM, Charles Pritchard ch...@jumis.com wrote:
On Dec 8, 2011, at 1:04 PM, Wenbo Zhu wen...@google.com wrote:
On Wed, Dec 7, 2011 at 6:04 PM, Charles Pritchard ch...@jumis.com
ch...@jumis.com wrote:
**
I think the Web Sockets spec is intended for client to
On Sun, 11 Dec 2011 15:44:58 +0100, Jarred Nicholls jar...@sencha.com
wrote:
I understand that's how you spec'ed it, but it's not how it's implemented
in IE nor WebKit for legacy purposes - which is what I meant in the above
statement.
What do you mean legacy purposes? responseType is a new
Hi,
I have reviewed all of the recent discussion and spent some time
analysing JQuery, and I have compiled this rough specification detailing
how I think find, findAll and matches can work. The following details
the rationale for each of the design decisions made.
The new methods should
I'd like to bring up an issue with the spec with regards to responseText +
the new json responseType. Currently it is written that responseText
should throw an exception if the responseType is not or text. I would
argue that responseText should also return the plain text when the type is
json.
I'd like to bring up an issue with the spec with regards to responseText +
the new json responseType. Currently it is written that responseText
should throw an exception if the responseType is not or text. I would
argue that responseText should also return the plain text when the type is
json.
On Sun, Dec 11, 2011 at 4:08 PM, Jarred Nicholls jar...@sencha.com wrote:
A good compromise would be to only throw it away (and thus restrict
responseText access) upon the first successful parse when accessing
.response.
I disagree. Even though conceptually, the spec says that you first
On 2011-12-11 13:55, Marcos Caceres wrote:
On Fri, 09 Dec 2011 19:51:48 +0100, Glenn Adamsgl...@skynav.com
(mailto:gl...@skynav.com) wrote:
If the answer is that no item() method is implied, then does the use of
sequenceT in these newer specs entail dropping this method (with
respect to
On Mon, Dec 12, 2011 at 5:37 AM, Anne van Kesteren ann...@opera.com wrote:
On Sun, 11 Dec 2011 15:44:58 +0100, Jarred Nicholls jar...@sencha.com
wrote:
I understand that's how you spec'ed it, but it's not how it's implemented
in IE nor WebKit for legacy purposes - which is what I meant in
On Mon, Dec 12, 2011 at 6:39 AM, Henri Sivonen hsivo...@iki.fi wrote:
On Sun, Dec 11, 2011 at 4:08 PM, Jarred Nicholls jar...@sencha.com
wrote:
A good compromise would be to only throw it away (and thus restrict
responseText access) upon the first successful parse when accessing
On Mon, 12 Dec 2011 14:12:57 +0100, Jarred Nicholls jar...@sencha.com
wrote:
I started an initiative to bring XHR in WebKit up-to-spec (see
https://bugs.webkit.org/show_bug.cgi?id=54162) and got a lot of push
back. All I'm asking is that if I run into push back again, that I can
send them
On 12/12/2011 03:12 PM, Jarred Nicholls wrote:
On Mon, Dec 12, 2011 at 5:37 AM, Anne van Kesteren ann...@opera.com
mailto:ann...@opera.com wrote:
On Sun, 11 Dec 2011 15:44:58 +0100, Jarred Nicholls
jar...@sencha.com mailto:jar...@sencha.com wrote:
I understand that's how you
Hi All - the CfCs to publish a WD of the new XHR [1] and a WG Note of
the old XHR [2] resulted in different opinions expressed. We think it is
important to provide a clear message (especially for those not closely
following WebApps' related discussions) that: 1) the group agreed to stop
One small typo correction below ...
On 12/12/11 8:47 AM, ext Charles McCathieNevile wrote:
Hi All - the CfCs to publish a WD of the new XHR [1] and a WG Note
of the old XHR [2] resulted in different opinions expressed. We
think it is important to provide a clear message (especially for those
On Mon, 12 Dec 2011 14:47:06 +0100, Charles McCathieNevile
cha...@opera.com wrote:
Hi All - the CfCs to publish a WD of the new XHR [1] and a WG Note of
the old XHR [2] resulted in different opinions expressed. We think it
is important to provide a clear message (especially for those not
Thanks for doing the work here, Lachlan! This appears to be an
excellent summary of the discussion and a consistent proposal.
On Mon, Dec 12, 2011 at 3:07 AM, Lachlan Hunt lachlan.h...@lachy.id.au wrote:
6. *Proposed IDL*
interface NodeSelector {
Element find(DOMString selectors, optional
On Mon, Dec 12, 2011 at 9:28 AM, Boris Zbarsky bzbar...@mit.edu wrote:
On 12/12/11 8:12 AM, Jarred Nicholls wrote:
I started an initiative to bring XHR in WebKit up-to-spec (see
https://bugs.webkit.org/show_**bug.cgi?id=54162https://bugs.webkit.org/show_bug.cgi?id=54162)
and got a lot of
Dear WebApps people,
The HTML Speech Incubator Group [1] has recently wrapped up its work on use
cases, requirements, and proposals for adding automatic speech recognition
(ASR) and text-to-speech (TTS) capabilities to HTML. The work of the group is
documented in the group's Final Report. [2]
17 matches
Mail list logo
