On Sun, Feb 8, 2009 at 9:20 PM, Ian Hickson i...@hixie.ch wrote:
On Sun, 8 Feb 2009, Garrett Smith wrote:
Sometimes a document's resources are not needed all at first. For
example, a script that is not needed until after the document is parsed
can be given the defer attribute (for browsers
On 1/17/09, Anne van Kesteren ann...@opera.com wrote:
On Sat, 17 Jan 2009 04:04:19 +0100, Jonas Sicking jo...@sicking.cc wrote:
Not sure if I should be posting this to the whatwg list or the webapps
list, given that the spec is in process of transitioning between the
two groups. So I'm posting
On 1/17/09, Anne van Kesteren ann...@opera.com wrote:
On Sat, 17 Jan 2009 19:24:56 +0100, Jonas Sicking jo...@sicking.cc wrote:
I'm talking about parity with other onX attributes inside workers.
But I'd be fine with changing onX for other objects if all other
browsers do something else
On Thu, Jan 15, 2009 at 4:54 PM, Ian Hickson i...@hixie.ch wrote:
On Thu, 15 Jan 2009, Jonas Sicking wrote:
On Thu, 17 Jul 2008, Jonas Sicking wrote:
Assuming there is something sane we can all agree on. So far that is not
the case. On both points :)
I think the current text
Hi All,
Not sure if I should be posting this to the whatwg list or the webapps
list, given that the spec is in process of transitioning between the
two groups. So I'm posting to both in the hope that this thread won't
generate too much related traffic. So please stay on topic :)
Currently the
On Thu, Jan 15, 2009 at 8:28 AM, Boris Zbarsky bzbar...@mit.edu wrote:
Kartikaya Gupta wrote:
sn = document.createElement( 'script' );
sn.setAttribute( 'type', 'text/javascript' );
document.body.appendChild( sn );// this *should* run an empty
script block and do nothing
That
On Thu, 17 Jul 2008, Jonas Sicking wrote:
Assuming there is something sane we can all agree on. So far that is not
the case. On both points :)
I think the current text in the spec is pretty reasonable at this point.
The main text is here:
http://www.whatwg.org/specs/web-apps/current
On Tue, Jan 13, 2009 at 1:41 AM, Ian Hickson i...@hixie.ch wrote:
On Mon, 28 Apr 2008, Brady Eidson wrote:
Anne was asserting that since the interface for setItem() specifies a
DOMString as the input, anything you pass it will be stringified.
Therefore passing it the null value would be
On Tue, Jan 13, 2009 at 4:48 AM, Anne van Kesteren ann...@opera.com wrote:
On Tue, 13 Jan 2009 13:44:22 +0100, Jonas Sicking jo...@sicking.cc wrote:
I talked with Cameron a while ago about what the default behavior
should be for null. We couldn't find any functions that required that
null
On Tue, Jan 13, 2009 at 3:37 PM, Cameron McCormack c...@mcc.id.au wrote:
Jonas Sicking:
I talked with Cameron a while ago about what the default behavior
should be for null. We couldn't find any functions that required that
null be treated as null, but there are several examples of functions
On Tue, Jan 13, 2009 at 4:26 PM, Cameron McCormack c...@mcc.id.au wrote:
Jonas Sicking:
So in the null column an S means that it's treated as null, an E
as , but what does N mean?
N means that I was able to determine that null was treated as the
actual null value, rather than converted
On Wed, Dec 31, 2008 at 4:59 AM, Ian Hickson i...@hixie.ch wrote:
On Wed, 31 Dec 2008, Jonas Sicking wrote:
On Wed, Dec 31, 2008 at 3:17 AM, Jonas Sicking jo...@sicking.cc wrote:
On Mon, Dec 29, 2008 at 11:37 AM, Ian Hickson i...@hixie.ch wrote:
On Fri, 22 Aug 2008, Shannon wrote:
Either
2008/12/30 Alexey Proskuryakov a...@webkit.org:
Dec 30, 2008, в 7:09 PM, timeless написал(а):
I suggest changing the signature to ^BOM?CACHE MANIFEST - then it
will
be easier to verify, and it will be possible to add comments at the end.
This is how we have it in WebKit now, and changing
On Mon, Dec 29, 2008 at 11:37 AM, Ian Hickson i...@hixie.ch wrote:
On Fri, 22 Aug 2008, Shannon wrote:
Either way I would recommend making a decision on minimum and maximum
integer values an using them consistently. If not I can imagine the
rapid adoption of 64-bit systems will cause
On Wed, Dec 31, 2008 at 3:17 AM, Jonas Sicking jo...@sicking.cc wrote:
On Mon, Dec 29, 2008 at 11:37 AM, Ian Hickson i...@hixie.ch wrote:
On Fri, 22 Aug 2008, Shannon wrote:
Either way I would recommend making a decision on minimum and maximum
integer values an using them consistently
On Sun, Dec 28, 2008 at 6:22 PM, Adam Barth wha...@adambarth.com wrote:
On Fri, 13 Jun 2008, Adam Barth wrote:
3) The document's origin and effective script origin become the origin
and the effective script origin of the currently executing script.
(Note: actually, the origins are aliased, as
On Wed, Dec 24, 2008 at 12:51 AM, Ian Hickson i...@hixie.ch wrote:
On Tue, 23 Dec 2008, Jonas Sicking wrote:
I ended up using a combination of both the event mechanism and the old
Window.onerror mechanism. The spec now says to fire onerror in the
worker global scope, using the old
On Tue, Dec 23, 2008 at 4:10 PM, Ian Hickson i...@hixie.ch wrote:
On Tue, 16 Dec 2008, Jonas Sicking wrote:
Ian Hickson wrote:
On Thu, 27 Nov 2008, ben turner wrote:
Assuming we have a page that creates a worker (let's call this
worker the parent), and it creates a new worker
This should work in any scenario in which the XSLT processor itself is
serializing the output. If it's merely generating some sort of DOM or tree
to pass to another process, then all bets are off. However in that scenario,
other means of producing DOCTYPES are also not guaranteed since the
Ian Hickson wrote:
On Thu, 27 Nov 2008, ben turner wrote:
I just got around to fixing the error handling in our worker
implementation and realized that the spec is a little vague here,
especially when workers are created within workers. This is what we have
now, and Jonas and I both find it
Currently tokenizing the following string (starting at Data state)
!--foo results in a parse error when hitting the 'f'. It seems like
the error is in the Comment start dash state (section 8.2.4.19). It
should switch to 'comment state' when a '-' is consumed, which is not
what it currently does.
I see the Element interface no more contains methods to handle Attr
nodes: since those are described as not being child nodes of an
Element, in W3C specifications, there will be any other way to handle
attributes as nodes, the 'nature' of Attr nodes is going to change, or
is there a too little
Otherwise, just let the id attribute be unique in the whole document, label
any duplicate one as illegal and treat it as the empty string, so that one
only method is enough and the DOM 3 undefined behaviour for 'getElementById'
is no more problematic, being fired by non-allowed DOM structures
Jonas Sicking wrote:
Ian Hickson wrote:
On Thu, 26 Jun 2008, Jonas Sicking wrote:
On Sat, 18 Aug 2007, Jonas Sicking wrote:
Since ID is case sensitive everywhere else, I don't see a reason to
make
an exception from that rule here. That seems to unnecessarily
complicate
implementation
On Fri, Nov 28, 2008 at 3:00 AM, Lachlan Hunt [EMAIL PROTECTED] wrote:
Jonas Sicking wrote:
Ian Hickson wrote:
On Thu, 26 Jun 2008, Jonas Sicking wrote:
What I did notice in our code though is how we deal with the case when
there are multiple maps with the same name. In this case we
On Sun, Nov 30, 2008 at 11:05 PM, Chris Double
[EMAIL PROTECTED] wrote:
On Mon, Dec 1, 2008 at 7:11 PM, Peter Kasting [EMAIL PROTECTED] wrote:
I don't think it is the end of the world if this attribute goes in, but I
see very little benefit to it, and I am always for removing items with
On Mon, Dec 1, 2008 at 12:37 AM, Ian Hickson [EMAIL PROTECTED] wrote:
On Mon, 1 Dec 2008, Jonas Sicking wrote:
Another thing, if I as a website developer find a video that was encoded
with the wrong pixel ratio, wouldn't the simplest, and most intuitive,
way to fix it be to simply set a width
On Mon, Dec 1, 2008 at 4:37 AM, Ian Hickson [EMAIL PROTECTED] wrote:
On Mon, 1 Dec 2008, Lachlan Hunt wrote:
Ian Hickson wrote:
On Mon, 1 Dec 2008, Jonas Sicking wrote:
Try the following markup in firefox:
map name=foo/map
map name=foo
area shape=circle coords
Ian Hickson wrote:
There's a question at the bottom about how best to make transactions be
free of concurrency problems. Input welcome.
On Fri, 23 May 2008, Aaron Boodman wrote:
I noticed one unfortunate thing about the new Database API. Because the
executeSql() callback holds open the
Pentasis wrote:
I was thinking mostly about the tag's current usage on the web, which
is a crazy mix between the HTML4 and HTML5 definition of the element.
HTML4 defines it purely presentational, HTML5 mostly semantical. In
that context, I believe small is inappropriate.
However, as you
Aaron Boodman wrote:
On Tue, Nov 18, 2008 at 10:09 PM, Dmitry Titov [EMAIL PROTECTED] wrote:
Ok, it makes sense for OOM to treat it as other OOM cases.
If I may ask your opinion about related thing: SharedWorkers potentially
would run cross-process. IPC can stop/stuck for many reasons, taret
Robert O'Callahan wrote:
On Mon, Nov 17, 2008 at 3:19 PM, Jonas Sicking [EMAIL PROTECTED] wrote:
Ian Hickson wrote:
Video and audio playback is already extremely CPU intensive,
we shouldn't require the UA to burn extra cycles doing
unnecessary work
Jeremy Doig wrote:
i would hope that repainting a progress bar that has not moved
50x/second would not be a normal implementation too. 2x/second seems
more realistic (a 300s video with a 600 pixel-wide playbar).
Well, pages are most likely going to update the progress bar as often as
we fire
Jeremy Doig wrote:
On Mon, Nov 17, 2008 at 3:05 PM, Jonas Sicking [EMAIL PROTECTED] wrote:
Jeremy Doig wrote:
i would hope that repainting a progress bar that has not moved
50x/second would not be a normal implementation too. 2x/second
seems more realistic (a 300s
, Jonas Sicking [EMAIL PROTECTED] wrote:
Hi All,
Ben just wrote up a patch to support JSON objects as well as primitive
values (0, null, false, etc) to be passed to and from workers using
postMessage.
Wanted to see what the reactions to this was. Is it a good idea or not?
I seem to recall this coming
(), then you could expand this in the future to also
allow blobs w/o changing anything about JSON.
- a
On Mon, Nov 17, 2008 at 8:10 PM, Jonas Sicking [EMAIL PROTECTED] wrote:
Indeed. Blobs is a great idea. We'll probably have to create further JSON
extensions to support that.
/ Jonas
Aaron Boodman
Ian Hickson wrote:
Video and audio playback is already extremely CPU intensive, we
shouldn't require the UA to burn extra cycles doing unnecessary work.
I agree. That was exactly the thinking behind the timeupdate event. It
allows the UA to determine how fast to update the UI without hurting
Alexey Proskuryakov wrote:
Nov 14, 2008, в 8:50 AM, Jonas Sicking написал(а):
To fix all this I propose that if a port has been started, we don't
allow it to be passed to postMessage. If that is done an exception is
thrown.
Could you please explain how this scenario is affected by the port
Alexey Proskuryakov wrote:
Nov 14, 2008, в 10:00 AM, Jonas Sicking написал(а):
What are the use cases? Also note that we can't use it with shared
workers since they can be connected to several pages from different
uris.
It returns the script's URL, not the page's.
Oh?! Then I understand
Alexey Proskuryakov wrote:
Nov 14, 2008, в 11:31 PM, Jonas Sicking написал(а):
Could you please explain how this scenario is affected by the port
being started? Messages are queued in closed ports until those are
started, so I think that it applies word to word to closed ports.
Where
Aaron Boodman wrote:
On Fri, Nov 14, 2008 at 4:33 PM, Jonas Sicking [EMAIL PROTECTED] wrote:
Hmm.. this makes a lot of sense for importScripts, but for XHR you probably
want the baseURI to be that of the opening page, since it's quite likely
that the opening page gave you a URI to open
Alexey Proskuryakov wrote:
Nov 6, 2008, в 2:18 AM, Jonas Sicking написал(а):
Similarly, having separate interfaces for Worker and SharedWorker
implies that there is some fundamental difference in their behavior -
a difference that eludes me so far.
A shared worker is shared between all
Here are my preference on changes, in descending order:
* Add a connect() method to Worker and/or SharedWorker
There has been lots of talk about this, but I'm still confused as to
what the exact proposals are due to lack of details. But here is my
interpretation
Details:
- Make instantiating a
Ian Hickson wrote:
On Fri, 14 Nov 2008, Shannon wrote:
I don't see any value in the user-agent specified amount of time delay
in stopping scripts. How can you write cleanup code when you have no
consistency in how long it gets to run (or if it runs at all)?
The user-agent specified amount of
On Thu, Nov 13, 2008 at 6:56 PM, Ian Hickson [EMAIL PROTECTED] wrote:
If I have missed a key point, please do let me know. It's quite
possible that I missed something when reading this thread as it was
quite long and had a lot of repetition.
Sounds good to me.
/ Jonas
Hi All,
It is currently possible (I think) to send a port through postMessage
after the port was started. This makes sending ports across processes
(such as to an iframe or worker living in a different process) pretty
painful to implement. It also makes it hard to define without causing
race
Aaron Boodman wrote:
On Thu, Nov 13, 2008 at 8:45 PM, Ian Hickson [EMAIL PROTECTED] wrote:
On Thu, 13 Nov 2008, Jonas Sicking wrote:
Actually, i think we should remove the location accessor as well. I
can't think of a common enough use case that warrants an explicit API.
You can always
Ian Hickson wrote:
On Thu, 13 Nov 2008, Jonas Sicking wrote:
Aaron Boodman wrote:
On Thu, Nov 13, 2008 at 8:45 PM, Ian Hickson [EMAIL PROTECTED] wrote:
On Thu, 13 Nov 2008, Jonas Sicking wrote:
Actually, i think we should remove the location accessor as well. I
can't think of a common enough
Ian Hickson wrote:
On Thu, 13 Nov 2008, Jonas Sicking wrote:
Honestly I'm not really sure why the spec says that you need a list at
all, other than maybe to talk about GC (which i've many times mentioned
I think the spec should not need to define).
I remembered what it was that I was trying
Ian Hickson wrote:
On Thu, 13 Nov 2008, Jonas Sicking wrote:
I don't really see how we can do away with this without interop
issues.
It sounds to me like simply saying:
setTimout(handler, ms):
When called will schedule a event 'ms' milliseconds after the function
is called. When the event
Maciej Stachowiak wrote:
On Nov 10, 2008, at 6:50 PM, Robert O'Callahan wrote:
Should video and audio elements be able to load and play resources
from other origins?
Perhaps Ian thinks not:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6104
There's a to-and-fro discussion here:
Tim Starling wrote:
Robert O'Callahan wrote:
Should video and audio elements be able to load and play resources
from other origins?
Perhaps Ian thinks not:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=6104
There's a to-and-fro discussion here:
The workers examples use 'event.message' in a bunch of places, however
the property is called 'event.data'. Same mistake in the View this
example online pages.
/ Jonas
Alexey Proskuryakov wrote:
Nov 5, 2008, в 11:06 PM, Aaron Boodman написал(а):
Jonas, Hixie, and I talked about this yesterday on IRC (logs start
here: http://krijnhoetmer.nl/irc-logs/whatwg/20081104#l-575 and go
into the next day).
...
* Remove startConversation() from the Worker interface
Ian Hickson wrote:
* Remove the port property from the SharedWorker interface and give it
a postMessage and onmessage just like dedicated workers have.
I really don't like this. With (Dedicated)Worker it makes sense because
both sides bury the underlying message channel and ports and so
Here's an example in code:
// dedicated workers (outside)
var worker = new Worker(foo.js);
var port = worker.connect();
port.onmessage = function() { }
port.postMessage(ping);
// dedicated workers (inside)
onconnect = function(e) {
e.port.onmessage = function(e) {
Jonas Sicking wrote:
Here's an example in code:
// dedicated workers (outside)
var worker = new Worker(foo.js);
var port = worker.connect();
port.onmessage = function() { }
port.postMessage(ping);
// dedicated workers (inside)
onconnect = function(e) {
e.port.onmessage = function(e
For future compat it would be good to expose to workers information on
what browser is currently being used. This can be used to work around
bugs and lack of features.
In a 'normal' window context the navigator object exposes a set of
properties, such as userAgent, that can be used for this
Eric Carlson wrote:
Ian -
On Oct 28, 2008, at 10:36 PM, Chris Double wrote:
On Wed, Oct 29, 2008 at 5:22 PM, Charles Iliya Krempeaux
[EMAIL PROTECTED] wrote:
Perhaps I didn't read the spec carefully enough, but I don't see any
such
event.
You're looking for the 'timeupdate' event. This
Only the globalscope is specified to implement EventTarget, the actual
Worker should too.
/ Jonas
Silvia Pfeiffer wrote:
On Sat, Oct 25, 2008 at 6:18 PM, Jonas Sicking [EMAIL PROTECTED] wrote:
After thinking about this, I'm not sure that limiting playback to a
section of a media file will be used very often. A developer can easily
script the same functionality as long as they don't use
Eduard Pascual wrote:
On Wed, Oct 29, 2008 at 6:16 PM, Jonas Sicking [EMAIL PROTECTED] wrote:
Maciej (and I think others) have suggested that it would be useful if it was
possible to allow audio to be used such that a single file can be
downloaded that contains multiple sound effects
On Oct 29, 2008, at 18:34, Silvia Pfeiffer
[EMAIL PROTECTED] wrote:
On Thu, Oct 30, 2008 at 11:52 AM, Jonas Sicking [EMAIL PROTECTED]
wrote:
Eduard Pascual wrote:
On Wed, Oct 29, 2008 at 6:16 PM, Jonas Sicking [EMAIL PROTECTED]
wrote:
Maciej (and I think others) have suggested
After thinking about this, I'm not sure that limiting playback to a
section of a media file will be used very often. A developer can easily
script the same functionality as long as they don't use the default
controller, so it seems to me that attributes for this aren't warranted.
I think they
Fabien Meghazi wrote:
Will it be possible for the browsers to allow an extension such as
canvas block ?
My understanding is that it won't be possible (please correct me if
I'm wrong, I'm not an expert) as the initialization of a canvas
context is done as follow :
var canvas =
Ian Hickson wrote:
Great! Thanks. I think your idea of making rel=help be relative to the
nearest parent label is a good one. We could also say it is relative to
the nearest parent label, body, section, form, fieldset, or
other such grouping element. I'll look at this in more detail when
Ian Hickson wrote:
2. select tag:
selectedindex=[num]
implicitly set the selected index, instead of having to parse all the option
tags and insert a selected string, much easier to bind to server side data,
an invalid value (such as -1 or greater than the number of option tags) would
mean
Chris Double wrote:
On Thu, Oct 16, 2008 at 4:07 PM, Eric Carlson [EMAIL PROTECTED] wrote:
However I also think
that playing just a segment of a media file will be a common use-case, so I
don't think we need start and end either.
How would you emulate end via JavaScript in a reasonably
Anne van Kesteren wrote:
On Wed, 15 Oct 2008 17:01:22 +0200, Sander van Zoest
[EMAIL PROTECTED] wrote:
I hate to say it, but if it was enough, I wouldn't be commenting here. It
simply isn't accurate
enough to store it as a float.
How is not accurate? In terms of precision it shouldn't really
Collin Jackson wrote:
6) New cookie attribute: The httpOnly cookie flag allows sites to
put restrictions on how a cookie can be accessed. We could allow a new
flag to be specified in the Set-Cookie header that is designed to
prevent CSRF and UI redress attacks. If a cookie is set with a
Russell Leggett wrote:
I've wrestled with this because its something that our designer has
wanted to use all over the place for an application I'm working on. It
turns out to be a usability nightmare if not used sparingly.
Why was it a uasability nightmare? Would it still have been a
Benjamin Hawkes-Lewis wrote:
Garrett Smith wrote:
|placeholder| sounds a little like |alt|. Alt is a property and an
attribute on INPUT.
How is placeholder content for a form field alternative text?
The alt text is for situations where the input can not be displayed at
all. For example an
Benjamin Hawkes-Lewis wrote:
Garrett Smith wrote:
|placeholder| sounds a little like |alt|. Alt is a property and an
attribute on INPUT.
How is placeholder content for a form field alternative text?
The alt text is for situations where the input can not be displayed at
all. For example an
Hi Guys,
Sorry about the slow feedback, has been on vacation most of the time.
So first off I don't think we can remove the ability to pass
MessagePorts around. This ability exists in Window.postMessage already
per spec so nothing that the workers spec does can change that. Also, if
we think
On Sat, Sep 20, 2008 at 12:37 PM, Ian Hickson [EMAIL PROTECTED] wrote:
On Sat, 20 Sep 2008, Keryx Web wrote:
BTW, Gecko had an implementation of the ping attribute they backed out
due to spec changes. Is that part of the spec stable enough for them to
start working on again?
I'm not aware
Anne van Kesteren wrote:
On Fri, 29 Aug 2008 16:20:21 +0200, Cameron McCormack [EMAIL PROTECTED]
wrote:
Robert O'Callahan:
Why not just open new window and move the playing audio element
from the old window into the new window? You might need to call
play() on it again in the new window, but
Some comments:
The spec currently says:
Once the WorkerGlobalScope's closing flag is set to true, the queue must
discard anything else that would be added to it. Effectively, once the
closing flag is true, timers stop firing, notifications for all pending
asynchronous operations are dropped,
Jonas Sicking wrote:
Some comments:
The spec currently says:
Once the WorkerGlobalScope's closing flag is set to true, the queue must
discard anything else that would be added to it. Effectively, once the
closing flag is true, timers stop firing, notifications for all pending
asynchronous
Aaron Boodman wrote:
I encounter sites frequently that want to pop out part of their
application free of the page, into a smaller window. For example,
Pandora radio (http://pandora.com) does this. The player starts out
embedded in the normal content area, but users have the option to pop
it out
Looks like the example code in 1.1.4 Shared workers does
worker.addEventListener rather than worker.port.addEventListener. I
assume this is a bug?
/ Jonas
Ian Hickson wrote:
On Wed, 20 Aug 2008, Jonas Sicking wrote:
Do we really need the SharedWorker interface. I.e. couldn't we just
return a MessagePort?
We could. It would mean either putting onerror on all message ports, or
not reporting error information for shared workers. Actually even
I have to say that I don't really agree with Hixie here either.
I think there is much value in letting HTML be a viable format for
document distribution outside the web. I definitely don't think of it as
a non-goal. Things like distributable cross-platform DVDs of wikipedia
containing just a
João Eiras wrote:
On , Jonas Sicking [EMAIL PROTECTED] wrote:
(...)
Here is the list of elements that we *don't* execute scripts inside of
in firefox:
http://mxr.mozilla.org/mozilla-central/source/content/base/src/nsScriptElement.cpp#148
i.e. iframe, noframes, noembed
Everywhere else
There is a race condition in proposed new Web Workers spec. The return
value from postMessage can in some cases be true, even if the worker
never receives the message.
For example:
main.js:
w = new DedicatedWorker(worker.js);
if (w.postMessage(hello there)) {
alert(success!!);
}
Simon Pieters wrote:
On Thu, 21 Aug 2008 23:54:44 +0200, Jonas Sicking [EMAIL PROTECTED] wrote:
Here is the list of elements that we *don't* execute scripts inside of
in firefox:
http://mxr.mozilla.org/mozilla-central/source/content/base/src/nsScriptElement.cpp#148
i.e. iframe, noframes
This is looking great. A few comments though (of course :) )
Do we really need the SharedWorker interface. I.e. couldn't we just
return a MessagePort? This would probably require that we use a factory
function rather than a constructor, like getPortForSharedWorker or
some such. In other
Shannon wrote:
Jonas Sicking wrote:
Shannon wrote:
I've been following the WebWorkers discussion for some time trying to
make sense of the problems it is trying to solve. I am starting to
come to the conclusion that it provides little not already provided by:
setTimeout(mainThreadFunc,1
João Eiras wrote:
Hi !
Not a long time ago, we saw an Opera build which had video support. What
was really really cool about it was that video was pretty much supported
like any other image format so we could apply filtering and other complex
stuff from svg like in this example.
ddailey wrote:
The Opera build with real-time SVG filters applied to video, made me
think that HTML and SVG ought to be sharing the filter business rather
than being mired down with the troglodytic canvas re-invention of
wheel business, but then who's to say that wheels need to be round
Shannon wrote:
I've been following the WebWorkers discussion for some time trying to
make sense of the problems it is trying to solve. I am starting to come
to the conclusion that it provides little not already provided by:
setTimeout(mainThreadFunc,1)
setTimeout(workThreadFunc,2)
One solution I thought about is to have a base interface such as:
interface MessagePort {
void postMessage(...);
attribute EventListener onmessage;
...
}
Then have
interface Worker : MessagePort {
bool isShared();
worker specific stuff
}
interface PipePort : MessagePort {
So the API I'm proposing is the following:
[NoInterfaceObject] interface WorkerFactory {
Worker createWorker(in DOMString scriptURL);
Worker createSharedWorker(in DOMString name, in DOMString scriptURL);
};
interface Worker {
boolean postMessage(in DOMString message);
boolean
Ian Hickson wrote:
On Fri, 8 Aug 2008, Jonas Sicking wrote:
So the API I'm proposing is the following:
This seems to be a strict subset of what the spec has now; the only
difference being that there's no easy way to create a worker and then pass
it to someone else to take care
This is something that have been in the back of my brain for a few days:
How do we deal with the user navigating a way from a page if there's a
Worker in the middle of some very long running script?
First off, please notice that this discussion is 100% orthogonal to the
communications API
Ian Hickson wrote:
On Fri, 8 Aug 2008, Jonas Sicking wrote:
(We might want to add an onconnect property to WorkerGlobalScope,
but it doesn't seem strictly needed)
How else would you connect to a shared worker?
That is done at an application level. For example:
worker = createSharedWorker(foo
Jonas Sicking wrote:
Ian Hickson wrote:
On Fri, 8 Aug 2008, Jonas Sicking wrote:
(We might want to add an onconnect property to WorkerGlobalScope,
but it doesn't seem strictly needed)
How else would you connect to a shared worker?
That is done at an application level. For example:
worker
Robert O'Callahan wrote:
http://www.w3.org/html/wg/html5/#dom-tree
1. If the |title| element
http://www.w3.org/html/wg/html5/#the-title1 is null, then a
new |title http://www.w3.org/html/wg/html5/#title1| element
must be created and appended to the |head|
Aaron Boodman wrote:
That's also one reason why I like having a separate Worker object and
having the two-step process of creating the worker, then sending it a
message. It means that creating a new channel to a worker is always
the same.
Hixie asked me on IRC why I didn't like the MessagePort
Ian Hickson wrote:
On Wed, 6 Aug 2008, Aaron Boodman wrote:
I am opposed to the utils object. I don't see any precedent for this
anywhere, and it just feels ugly to me. I liked it the way you had it
before, with these APIs in a shared base interface.
Ok. I don't have an opinion on this.
Dave Singer wrote:
At 20:10 +1200 7/08/08, Chris Double wrote:
On Thu, Aug 7, 2008 at 6:20 PM, Ian Hickson [EMAIL PROTECTED] wrote:
On Thu, 7 Aug 2008, Biju [EMAIL PROTECTED] wrote:
On Thu, Aug 7, 2008 at 1:49 AM, Ian Hickson [EMAIL PROTECTED] wrote:
playbackRate is the right way to do
801 - 900 of 984 matches
Mail list logo
