Ian Hickson, 2012-10-27 03:14 (Europe/Helsinki):
On Thu, 9 Aug 2012, Jussi Kalliokoski wrote:
On W3C AudioWG we're currently discussing the possibility of having web
workers that run in a priority/RT thread. This would be highly useful
for example to keep audio from glitching even under
Johan Sundström oyas...@gmail.com wrote:
Hi everybody!
Serializing a complete HTML document DOM to a string is surprisingly
hard in javascript.
Does XMLSerializer().serializeToString(document) not meet your requirement?
--
Stewart Brodie
Team Leader - ANT Galio Browser
ANT Software
On Sat, Oct 27, 2012 at 3:14 AM, Ian Hickson i...@hixie.ch wrote:
On Thu, 9 Aug 2012, Jussi Kalliokoski wrote:
On W3C AudioWG we're currently discussing the possibility of having web
workers that run in a priority/RT thread. This would be highly useful
for example to keep audio from
SZs
--
Sent using BlackBerry
- Original Message -
From: whatwg-requ...@lists.whatwg.org [mailto:whatwg-requ...@lists.whatwg.org]
Sent: Tuesday, October 30, 2012 06:39 AM
To: whatwg@lists.whatwg.org whatwg@lists.whatwg.org
Subject: whatwg Digest, Vol 103, Issue 51
On 30 Oct 2012 at 10:20, Stewart Brodie stewart.bro...@antplc.com wrote:
Johan Sundström oyas...@gmail.com wrote:
Serializing a complete HTML document DOM to a string is surprisingly
hard in javascript.
Does XMLSerializer().serializeToString(document) not meet your requirement?
I was
On Fri, 26 Oct 2012 17:23:53 +0300, Anne van Kesteren ann...@annevk.nl
wrote:
Currently encoding the query component of a URL using the document's
encoding affects all URLs with a relative scheme (http/ws/file/...).
Should we restrict this to http/https/file so new schemes such as
ws/wss and
On Mon, Oct 29, 2012 at 4:24 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 10/29/12 10:53 AM, Anne van Kesteren wrote:
But at that point in a URL you cannot have a path. A path starts with
a slash after the host.
The point is that on Windows, Gecko parses file://c:/something as
On 10/30/12 12:25 PM, Anne van Kesteren wrote:
Thanks, I missed that. It seems however we could have that parsing
rule for all platforms without issue, no?
Hmm. Possibly, yes. I'd love feedback from other UAs here!
-Boris
On Tue, 30 Oct 2012 17:20:33 +0200, Simon Pieters sim...@opera.com wrote:
On Fri, 26 Oct 2012 17:23:53 +0300, Anne van Kesteren ann...@annevk.nl
wrote:
Currently encoding the query component of a URL using the document's
encoding affects all URLs with a relative scheme (http/ws/file/...).
On 10/30/12 11:43 AM, Simon Pieters wrote:
The above applies to what gets sent over the wire when using the
WebSocket(...) constructor. For a href, the results are different:
http://simon.html5.org/test/url/url-encoding.html
I don't have an opinion at this point about what to do here.
In
On Tue, Oct 30, 2012 at 5:51 PM, Boris Zbarsky bzbar...@mit.edu wrote:
I would not be opposed to us explicitly specifying things this way. That
would incidentally require specs to say exactly when some non-UTF8 encoding
is supposed to be used for their URIs and what that encoding should be,
On Tue, 30 Oct 2012, Simon Pieters wrote:
On Fri, 26 Oct 2012 17:23:53 +0300, Anne van Kesteren ann...@annevk.nl
wrote:
Currently encoding the query component of a URL using the document's
encoding affects all URLs with a relative scheme (http/ws/file/...).
Should we restrict this to
On Tue, 30 Oct 2012 18:38:46 +0200, Boris Zbarsky bzbar...@mit.edu wrote:
On 10/30/12 12:25 PM, Anne van Kesteren wrote:
Thanks, I missed that. It seems however we could have that parsing
rule for all platforms without issue, no?
Hmm. Possibly, yes. I'd love feedback from other UAs here!
On Tue, 30 Oct 2012 16:25:30 -, Anne van Kesteren ann...@annevk.nl
wrote:
On Mon, Oct 29, 2012 at 4:24 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 10/29/12 10:53 AM, Anne van Kesteren wrote:
But at that point in a URL you cannot have a path. A path starts with
a slash after the host.
14 matches
Mail list logo
