Shouldn't setting onmessage on a Worker object enable the port message
queue?
Currently step 8 of the run a worker algorithm enables the port message
queue for the WorkerGlobalObjectScope side, but it is never enabled when
going in the other direction, if I'm reading the spec correctly.
Since we are no longer using progress events for media elements we don't
have the external requirement that abort/error shouldn't bubble. I'd like
them to bubble, because:
1. error events fired on source will bubble to video, which is quite
useful if one doesn't particularly care which
On Wed, 11 Nov 2009 16:05:53 +0100, Simon Pieters sim...@opera.com wrote:
Shouldn't setting onmessage on a Worker object enable the port message
queue?
Currently step 8 of the run a worker algorithm enables the port
message queue for the WorkerGlobalObjectScope side, but it is never
For reference see section 6.10.2 of the spec.
In getting an implementation for pushState(), replaceState(), and clearState()
going I've had a few concerns.
pushState() and replaceState():
When pushState() or replaceState() are called with a URL argument, the
document's current address is
I've been playing with the microdata DOM APIs again, continuing the
JavaScript experimental implementation http://gitorious.org/microdatajs.
It's not small or elegant, but at least some spec issues have come up in
the process.
What is the http://www.w3.org/1999/xhtml/microdata# URI? Just
Hi,
This is a new proposal taking into account the feedback I recieved to
the [WebWorkers] About the delegation example message.
In the delegation example of the WebWorker spec, we can see this line :
var num_workers = 10;
My concern is about the arbitrarity of the 10.
Regarding the hardware,
On 11/11/09 10:19 PM, David Bruant wrote:
This attribute have the following properties :
- It's only dependant on the hardware, the operating system and the
WebWorker implementation (thus, it is not dynamically computed by the
user agent at each call and two calls in the same
On 11/11/09 11:16 PM, Aryeh Gregor wrote:
I'm pretty sure that XHR is used for screen-scraping beyond Wikipedia,
Since it'd fail any time the data is not well-formed XML, I'd actually
expect such usage to be rare. It's not all that common to find XHTML
on the web that happens to be
I already filed a bug
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8268, but figured I'd
copy it here to get more discussion.
Wikipedia just experimented with switching to an HTML5 doctype. A lot
of user tools broke, and after two hours of investigation, we
determined that the problem is
On Wed, Nov 11, 2009 at 11:39 PM, Boris Zbarsky bzbar...@mit.edu wrote:
Since it'd fail any time the data is not well-formed XML, I'd actually
expect such usage to be rare. It's not all that common to find XHTML on
the web that happens to be well-formed XML.
A number of popular web apps
On 11/11/09 11:57 PM, Aryeh Gregor wrote:
A number of popular web apps output mostly well-formed XML, as far as
I know: vBulletin, WordPress, etc.
I assume you meant mostly as in most of the pages are well-formed,
not pages are mostly well-formed, since the latter is useless, right?
I did a
I'm not exactly sure what you mean in the first case. How is the title
change hidden from the DOM? When you call document.title = new title, then
the title does change in the DOM and in the UI.
About your second question, I think you misunderstood it. As you said, it
says:
Then, if the current
12 matches
Mail list logo
