On Tue, Mar 30, 2010 at 9:56 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 3/30/10 10:22 AM, Jonas Sicking wrote:
Making it implementation dependent is likely to lead to website
incompatibilities. Such as:
ws = new WebSocket(...);
ws.onopen = function() {
ws.send(someString);
if
On Tue, 30 Mar 2010 17:22:07 +0300, Jonas Sicking jo...@sicking.cc wrote:
On Tue, Mar 30, 2010 at 1:51 AM, Niklas Beischer n...@opera.com wrote:
On Tue, 30 Mar 2010 09:19:33 +0300, Jonas Sicking jo...@sicking.cc
wrote:
On Wed, Mar 24, 2010 at 2:33 PM, Ian Hickson i...@hixie.ch wrote:
On
On Wed, 31 Mar 2010 09:38:21 +0300, Jonas Sicking jo...@sicking.cc wrote:
On Tue, Mar 30, 2010 at 9:56 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 3/30/10 10:22 AM, Jonas Sicking wrote:
Making it implementation dependent is likely to lead to website
incompatibilities. Such as:
ws = new
On 31 March 2010 02:07, Richard Watts r...@kynesim.co.uk wrote:
Given what I've seen of the utter incomprehension the computing
strategy people in general have of video, I suspect the actual reason
for resistance is some form of pure political idiocy centering on the
mobile companies
My statement was completely wrong. Nokia isn't in the H.264 pool.
Here's the full list (PDF linked from this page):
http://www.mpegla.com/main/programs/AVC/Pages/PatentList.aspx
My sincere apologies to Nokia for this claim.
- d.
On 31 March 2010 08:48, Aaron Franco aa...@ngrinder.com wrote:
On 29 March 2010 00:03, Silvia Pfeiffer silviapfeiff...@gmail.com wrote:
On Mon, Mar 29, 2010 at 7:14 AM, David Gerard dger...@gmail.com wrote:
The catch with Vorbis is that if you support it, whoever owns the MP3
patents charges you a lot more.
(That's why I have an MP3 player that does Ogg
On 3/31/10 7:12 AM, Henri Sivonen wrote:
Currently, the spec says that document.open() sets the document's character encoding to UTF-16.
This is what IE does except IE uses the label unicode instead of UTF-16.
Demo: http://software.hixie.ch/utilities/js/live-dom-viewer/saved/438
Gecko and
On Mar 31, 2010, at 16:24, Boris Zbarsky wrote:
On 3/31/10 7:12 AM, Henri Sivonen wrote:
Currently, the spec says that document.open() sets the document's character
encoding to UTF-16. This is what IE does except IE uses the label unicode
instead of UTF-16.
Demo:
On Tue, 30 Mar 2010 15:09:49 -0700, Ian Hickson i...@hixie.ch wrote:
On Tue, 30 Mar 2010, Jonas Sicking wrote:
Personally my guess it's more likely that they really wanted to.
I have no idea which is more likely. The only use case I'm aware of is
passing an img in, and for that there isn't
Hi,
When implementing the close() function for Firefox we chose to set the
closing flag and clear pending events only. As the worker script is
calling close() on itself we figured that the worker should retain
maximum functionality until it has finished execution (otherwise it
could just not call
On Wed, 31 Mar 2010, Anne van Kesteren wrote:
On Tue, 30 Mar 2010 15:09:49 -0700, Ian Hickson i...@hixie.ch wrote:
On Tue, 30 Mar 2010, Jonas Sicking wrote:
Personally my guess it's more likely that they really wanted to.
I have no idea which is more likely. The only use case I'm aware
I see, thanks for the details!
This makes sense - you let the worker run unrestricted (ports still send
messages, sync API work) until it exits JS code. It is one of two
possibilities I though of as well (run unrestricted while in JS or immediate
termination).
BTW, the current Worker spec and
On 3/31/10 10:37 AM, Henri Sivonen wrote:
Gecko sets the document's character encoding to UTF-8 and uses UTF-8 to decode
the external resource.
One more clarifying question Does Gecko use UTF-8, or the encoding
of whatever document it was open() got called on?
WebKit uses the encoding
On Tue, Mar 30, 2010 at 11:06 PM, Niklas Beischer n...@opera.com wrote:
On Tue, 30 Mar 2010 17:22:07 +0300, Jonas Sicking jo...@sicking.cc wrote:
On Tue, Mar 30, 2010 at 1:51 AM, Niklas Beischer n...@opera.com wrote:
On Tue, 30 Mar 2010 09:19:33 +0300, Jonas Sicking jo...@sicking.cc
wrote:
On 3/31/10 2:38 AM, Jonas Sicking wrote:
I would have expected bufferedAmount to only change as a result of an
event being posted to the main event loop. We generally try to avoid
racy variables since people don't expect them. Consider for example
if (ws.bufferedAmount X) {
On Wed, Mar 31, 2010 at 3:16 PM, Boris Zbarsky bzbar...@mit.edu wrote:
On 3/31/10 2:38 AM, Jonas Sicking wrote:
I would have expected bufferedAmount to only change as a result of an
event being posted to the main event loop. We generally try to avoid
racy variables since people don't expect
Hi,
There is a typo on selection API name:
http://www.whatwg.org/specs/web-apps/current-work/#selection
selection . collapsed(parentNode, offset)
Replaces the selection with an empty one at the given position.
Throws a WRONG_DOCUMENT_ERR exception if the given node is in a different
document.
Henri Sivonen wrote:
Spec change request: Please change the spec to say that document.open()
sets the document's character encoding to UTF-8
+1. UTF-16 is a troublesome encoding for [X]HTML[5] documents and should
be consistently discouraged; as a ASCII-non-superset it interacts very
poorly
18 matches
Mail list logo
