On Thu, Jan 10, 2013 at 10:29 PM, Adam Barth w...@adambarth.com wrote:
Yes, agreed. For what it's worth, I believe Gecko recently made history not
accessible cross-origin anymore, so with any luck you'll be able to make
this change too if desired...
Do you have a link to the bug where that
Hixie wrote in https://www.w3.org/Bugs/Public/show_bug.cgi?id=18669#c31 :
I think it's fine for this not to work in XML, or require XML changes,
or use an attribute like xml:component= in XML. It's not going to
be used in XML much anyway in practice. I've already had browser
vendors ask me how
On Fri, Jan 11, 2013 at 8:26 AM, Matt Falkenhagen fal...@chromium.org wrote:
The Fullscreen spec says, for an element in the top layer:
If its specified position property is static, it computes to absolute.[1]
I think this is to make top layer elements out of flow. But then shouldn't
position
On Fri, Jan 11, 2013 at 11:40 AM, Anne van Kesteren ann...@annevk.nl wrote:
Yeah, I did not carefully review the suggestion from
http://lists.w3.org/Archives/Public/public-webapps/2012AprJun/0970.html
it seems. :-(
Fixed:
Hi Ashley,
I brought this very topic up in the latest W3C performance workgroup
meeting but pretty much all of my ideas were cut off due to a number of
parties believing that these are ultimately UA-specific (browser specific)
concerns, and should be dealt with at the browser level.
Jason Weber
On 1/11/13 1:29 AM, Adam Barth wrote:
On Wed, Jan 9, 2013 at 8:21 PM, Boris Zbarsky bzbar...@mit.edu wrote:
Yes, agreed. For what it's worth, I believe Gecko recently made history not
accessible cross-origin anymore
Do you have a link to the bug where that change was made?
On Fri, Jan 11, 2013 at 12:29:42PM +0200, Henri Sivonen wrote:
I think it would be a mistake to change HTML in such a way that it
would no longer fit into the XML data model *as implemented* and
thereby limit the range of existing software that could be used
outside browsers for working with
On Wed, Jan 9, 2013 at 8:00 AM, Ashley Gullen ash...@scirra.com wrote:
Some developers are starting to design large scale games using our HTML5
game engine, and we're finding we're running in to memory management
issues. Consider a device with 50mb of texture memory available. A game
might
On Wed, Jan 9, 2013 at 1:42 PM, Anne van Kesteren ann...@annevk.nl wrote:
My bad, I actually meant if a's associated shadow tree had an
insertion point through which a's child, which is b, would go and
then the event would be dispatched in b's associated shadow tree. (I
phrased that beyond
On Fri, Jan 11, 2013 at 6:50 PM, Dimitri Glazkov dglaz...@chromium.org wrote:
On Wed, Jan 9, 2013 at 1:42 PM, Anne van Kesteren ann...@annevk.nl wrote:
My bad, I actually meant if a's associated shadow tree had an
insertion point through which a's child, which is b, would go and
then the event
On Fri, Jan 11, 2013 at 10:10 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Fri, Jan 11, 2013 at 6:50 PM, Dimitri Glazkov dglaz...@chromium.org
wrote:
On Wed, Jan 9, 2013 at 1:42 PM, Anne van Kesteren ann...@annevk.nl wrote:
My bad, I actually meant if a's associated shadow tree had an
On Fri, Jan 11, 2013 at 7:56 PM, Dimitri Glazkov dglaz...@chromium.org wrote:
Can you elaborate on this a bit more. Note, you don't need to compute
offsetX/Y until they are actually requested (which is what WebKit does
anyway).
I see. That would change matters indeed.
Is that the case for all
On Fri, Jan 11, 2013 at 7:56 PM, Dimitri Glazkov dglaz...@chromium.org wrote:
On Fri, Jan 11, 2013 at 10:10 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Fri, Jan 11, 2013 at 6:50 PM, Dimitri Glazkov dglaz...@chromium.org
wrote:
Okay, so event path would be (in tree order):
a -- [shadow
On Fri, Jan 11, 2013 at 11:12 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Fri, Jan 11, 2013 at 7:56 PM, Dimitri Glazkov dglaz...@chromium.org
wrote:
Can you elaborate on this a bit more. Note, you don't need to compute
offsetX/Y until they are actually requested (which is what WebKit
On Fri, Jan 11, 2013 at 11:14 AM, Anne van Kesteren ann...@annevk.nl wrote:
Normally with b being a child of a there would not be any
adjustment.
Yup. I don't understand whether you're just agreeing with me or disagreeing
:)
With shadow trees in place, we need to let them react to events
On Fri, Jan 11, 2013 at 8:16 PM, Dimitri Glazkov dglaz...@chromium.org wrote:
On Fri, Jan 11, 2013 at 11:12 AM, Anne van Kesteren ann...@annevk.nl wrote:
Is that the case for all non-target/relatedTarget attributes that need
adjustment? That they do not actually need to be adjusted but are
On Fri, Jan 11, 2013 at 11:28 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Fri, Jan 11, 2013 at 8:16 PM, Dimitri Glazkov dglaz...@chromium.org
wrote:
On Fri, Jan 11, 2013 at 11:12 AM, Anne van Kesteren ann...@annevk.nl wrote:
Is that the case for all non-target/relatedTarget attributes
On Fri, Jan 11, 2013 at 8:31 PM, Dimitri Glazkov dglaz...@chromium.org wrote:
Sure. Where are you seeing this list being mentioned? In Shadow DOM
spec or in DOM Core spec? I am happy to help, just not sure what
exactly I need to be doing :)
I want you to create a list :-) Which attributes are
On Fri, 11 Jan 2013, Henri Sivonen wrote:
Hixie wrote in https://www.w3.org/Bugs/Public/show_bug.cgi?id=18669#c31 :
I think it's fine for this not to work in XML, or require XML changes,
or use an attribute like xml:component= in XML. It's not going to be
used in XML much anyway in
From: Ian Hickson [mailto:i...@hixie.ch]
On Thu, 10 Jan 2013, Thomas A. Fine wrote:
Use Cases:
4. Clarifying sentence boundaries would be an aid in machine
translation software.
Do you have any evidence supporting this? I've spoken with engineers who
work on machine translation
From: Ian Hickson [mailto:i...@hixie.ch]
To: Henri Sivonen
On Fri, 11 Jan 2013, Henri Sivonen wrote:
Hixie wrote in https://www.w3.org/Bugs/Public/show_bug.cgi?id=18669#c31 :
I think it's fine for this not to work in XML, or require XML
changes, or use an attribute like xml:component= in
On Sat, Jan 12, 2013 at 6:41 AM, Rik Cabanier caban...@gmail.com wrote:
Some of you concerns with memory management could be addressed with
WeakMaps.
Basically, you can put all your images in a WeakMap and during the draw
cycle, you pull them out and use them. If they're no longer there, it
On Fri, Jan 11, 2013 at 2:36 PM, Robert O'Callahan rob...@ocallahan.orgwrote:
On Sat, Jan 12, 2013 at 6:41 AM, Rik Cabanier caban...@gmail.com wrote:
Some of you concerns with memory management could be addressed with
WeakMaps.
Basically, you can put all your images in a WeakMap and during
On Sat, 12 Jan 2013, Vipul S. Chawathe wrote:
I'm doing some related work that requires machine translation on the lines
of export/import HTML snippets. Human language content boundaries are
directly determined by author's grammatical punctuation skills at the
sentence level.
Sure, but if
Ian Hickson wrote:
On Fri, 11 Jan 2013, Henri Sivonen wrote:
Hixie wrote in https://www.w3.org/Bugs/Public/show_bug.cgi?id=18669#c31 :
I think it's fine for this not to work in XML, or require XML changes,
or use an attribute like xml:component= in XML. It's not going to be
used in
On Fri, Jan 11, 2013 at 11:56 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Fri, Jan 11, 2013 at 8:31 PM, Dimitri Glazkov dglaz...@chromium.org
wrote:
Sure. Where are you seeing this list being mentioned? In Shadow DOM
spec or in DOM Core spec? I am happy to help, just not sure what
26 matches
Mail list logo
