On Thu, 13 Jan 2011 22:15:09 +0100, Boris Zbarsky bzbar...@mit.edu wrote:
Do current browsers implement the structured clones already ?
Firefox 4 does, for postMessage to workers (but not yet to other
windows; known bug). I'm not sure about others.
Opera since 10.60 supports structured
On Thu, 13 Jan 2011 22:05:54 +0100, Aryeh Gregor
simetrical+...@gmail.com wrote:
There are a bunch of places where it says When invoked with the same
argument the same NodeList object may be returned as returned by an
earlier call. Shouldn't this be either required or prohibited in any
given
Hi everyone,
Over the last months I have worked with several people at Google who
are amongst else from areas of accessibility, YouTube, Google Video,
Google Chrome and WebM. We have analysed the track specification and
the WebVTT (former WebSRT) specification mostly from a captioning
point of
Another relevant precedent is window.getSelection().modify (Webkit and
Gecko-2 specific), which uses the strings forward and backward to
specify the direction in which to alter the selection. English is not
my native language, and I'm not sure what the semantic difference
between forward and
On 01/13/2011 10:05 PM, Aryeh Gregor wrote:
In defining the interface for Node, some of the attributes are defined
like The parentElement attribute must return the parent node of the
context node if there is a parent and it is an Element node, or null
otherwise. while others are defined like
On 13/01/2011, at 22:15, Boris Zbarsky wrote:
On 1/13/11 3:19 PM, Jorge wrote:
I think so too for objects composed only of data properties, but what about
methods ? getters ? setters ? and prototypes ?
Maybe. It'd certainly take more work, and might start depending on exactly
how your
On Fri, Jan 14, 2011 at 11:41 PM, James Graham jgra...@opera.com wrote:
On 01/13/2011 10:05 PM, Aryeh Gregor wrote:
There are a bunch of places where it says When invoked with the same
argument the same NodeList object may be returned as returned by an
earlier call. Shouldn't this be
On 14/01/2011, at 09:32, Simon Pieters wrote:
On Thu, 13 Jan 2011 22:15:09 +0100, Boris Zbarsky bzbar...@mit.edu wrote:
Do current browsers implement the structured clones already ?
Firefox 4 does, for postMessage to workers (but not yet to other windows;
known bug). I'm not sure about
On 14 January 2011 10:16, Marijn Haverbeke mari...@gmail.com wrote:
Another relevant precedent is window.getSelection().modify (Webkit and
Gecko-2 specific), which uses the strings forward and backward to
specify the direction in which to alter the selection. English is not
my native language,
On 13/01/2011, at 22:15, Boris Zbarsky wrote:
On 1/13/11 3:19 PM, Jorge wrote:
On 13/01/2011, at 15:41, Boris Zbarsky wrote:
On 1/13/11 7:24 AM, Jorge wrote:
Not too long ago, the browsers did allow timeouts of less than 10ms.
Uh, no. Not too long ago browsers did not allow timeouts of
If you don't need the TextRange-like character-based modification, you
can instead use the selection's extend() method (supported in Mozilla,
WebKit and Opera for years) to create a backwards selection:
Maybe that is what you meant by this not working for TextRange-like
things, but,
On 14 January 2011 11:33, Marijn Haverbeke mari...@gmail.com wrote:
If you don't need the TextRange-like character-based modification, you
can instead use the selection's extend() method (supported in Mozilla,
WebKit and Opera for years) to create a backwards selection:
Maybe that is what you
Boris Zbarsky wrote:
It would be interesting to have an API that allows passing
an imagedata object (not a copy) to a worker. Such an API
would have to make the data disappear on the caller's side.
That could be implemented reasonably efficiently using
shared memory (either directly with
Diogo Resende wrote:
I see already information on the latest draft about a load
and error event, I think this is it. I was hoping some
browser vendors would implement it sooner :)
Yes, ironically link.onload works in IE6, but not in current
stable versions of Firefox, Safari or Chrome :-P
On 1/14/11 2:05 AM, Charles Pritchard wrote:
I've noticed, recently, that FF4b8 on Windows has a minimum
window.innerWidth of 392px.
For what it's worth, that's more or less a bug. It happens due to the
details of the UI structure (e.g. the url bar width can't shrink below a
certain amount)
On Fri, 14 Jan 2011 15:04:11 +0100, Boris Zbarsky bzbar...@mit.edu wrote:
On 1/14/11 2:05 AM, Charles Pritchard wrote:
I don't know that FF supports matchMedia
http://dev.w3.org/csswg/cssom-view/#dom-window-matchmedia
Not yet. I don't believe we've even reviewed that proposal for sanity
On 1/14/11 5:42 AM, Jorge wrote:
Are you sure there's really a maybe for methods ?
Methods' functions have access to (at least) the sender's global context and
contexts can't be shared, how to deal with that if not by prohibiting methods ?
We might need some ES spec changes/additions to
On 1/14/11 5:53 AM, Robert O'Callahan wrote:
... except I guess it can, because it could set expando properties on the
old NodeList and check for their presence later. Sigh.
We could make expandos on nodelists pin them so they can't be collected
as long as they can be reached via DOM APIs;
On 1/14/11 6:15 AM, Jorge wrote:
But in order to measure such short setTimeout()s I needed to know whether +new
Date() had enough resolution (*)
OK, yes.
Cool. What's the right place to start lobbying for it :-) ?
File a bug? ;) (Either on the spec or on browsers, depending on whom
you
On Fri, Jan 14, 2011 at 2:08 PM, Mike Wilson mike...@hotmail.com wrote:
Diogo Resende wrote:
I see already information on the latest draft about a load
and error event, I think this is it. I was hoping some
browser vendors would implement it sooner :)
Yes, ironically link.onload works in
On Fri, Jan 14, 2011 at 3:09 AM, Tim Down timd...@gmail.com wrote:
If you don't need the TextRange-like character-based modification, you
can instead use the selection's extend() method (supported in Mozilla,
WebKit and Opera for years) to create a backwards selection:
function
Maybe we can spec this so that regular selection primitives work properly
for textarea/input. e.g. you can expect that when
startContainer/endContainer is textarea/input, selection is set inside
textarea/input.
That would work for me, however, it'd be backwards-incompatible -- not
in a
On Fri, Jan 14, 2011 at 11:42 AM, Marijn Haverbeke mari...@gmail.comwrote:
That would work for me, however, it'd be backwards-incompatible -- not
in a critical way, but probably enough to break a few pieces of code.
Also, I assume there is a reason that textarea/textinput content is
not
If you accept that other selection APIs can't be used in textarea / input,
then why would you expect your property/method to specify direction can be?
Because I proposed it as *only* working for input fields.
Specifically that this direction property/method works for textarea / input
and
In section 4.4.5 (the aside element), an example is given that shows nav
being used within footer.
Section 4.4.3 (the nav element), explains that this would be an inappropriate
use of nav (http://dev.w3.org/html5/spec/Overview.html#the-nav-element):
Not all groups of links on a page need to be
On Fri, 14 Jan 2011, Nicholas Zakas wrote:
In section 4.4.5 (the aside element), an example is given that shows
nav being used within footer.
Section 4.4.3 (the nav element), explains that this would be an
inappropriate use of nav
Ah, I misinterpreted. With this in mind, I'm a bit unclear as to when nav
should be used. If it's intended for primary navigation but secondary
navigation can also be marked up with it, does that mean it's best to use nav
whenever you have more than one link grouped together?
Thanks.
27 matches
Mail list logo
