Hi,
Since last HTML Imports WD is published, I heard some feedback. Most of
them are about the loading order and its sync/async nature. Thanks for
sharing your thought!
At the same time, I found there are some confusion about how it works. As
it's hard for me to capture the underlying thinking
On Wed, 04 Dec 2013 18:58:10 +0100, Scott Miles sjmi...@google.com wrote:
seems a specification that seems really pushed/rushed
Since my team (Polymer) has been working with imports in practice for a
year-and-a-half (100% public and open-source, btw) this seems a strange
conclusion.
As
I've been putting off a response on this, but I have some things to add...
The topic on this thread was originally HTML Imports - it seems like some
of the concerns expressed extend beyond imports and are a little wider
ranging. I am cross posting this comment to public-next...@w3.org as I
think
To be fair though Web Components are bleeding edge and the vast
majority of developers have had no interaction with them at all.
I work in a company that should see huge benefits from Web Components
as we build large scale browser applications and not one developer has
had the time to investigate
On Wed, Dec 4, 2013 at 4:32 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Wed, Dec 4, 2013 at 9:21 AM, Brian Di Palma off...@gmail.com wrote:
I would say though that I get the feeling that Web Components seems a
specification that seems really pushed/rushed and I worry that might
lead
seems a specification that seems really pushed/rushed
Since my team (Polymer) has been working with imports in practice for a
year-and-a-half (100% public and open-source, btw) this seems a strange
conclusion. But this is only my perspective, I'm still a standards n00b I
suppose.
In any case, I
On Wed, Dec 4, 2013 at 9:56 AM, Dimitri Glazkov dglaz...@chromium.orgwrote:
On Wed, Dec 4, 2013 at 4:32 AM, Anne van Kesteren ann...@annevk.nlwrote:
On Wed, Dec 4, 2013 at 9:21 AM, Brian Di Palma off...@gmail.com wrote:
I would say though that I get the feeling that Web Components seems a
* Anne van Kesteren wrote:
On Wed, Dec 4, 2013 at 9:21 AM, Brian Di Palma off...@gmail.com wrote:
I would say though that I get the feeling that Web Components seems a
specification that seems really pushed/rushed and I worry that might
lead to some poor design decisions whose side effects will
On Wed, Dec 4, 2013 at 10:37 AM, Dimitri Glazkov dglaz...@chromium.orgwrote:
On Wed, Dec 4, 2013 at 9:56 AM, Dimitri Glazkov dglaz...@chromium.orgwrote:
On Wed, Dec 4, 2013 at 4:32 AM, Anne van Kesteren ann...@annevk.nlwrote:
On Wed, Dec 4, 2013 at 9:21 AM, Brian Di Palma off...@gmail.com
I never meant my comments to be taken as a slight toward anyone
involved in the Web Components work.
Neither did I mean it to be taken to mean This work is rushed. I said,
I get the feeling that Web Components seems a specification that
seems really pushed/rushed,
by that I meant it seemed as if
* Brian Di Palma wrote:
Neither did I mean it to be taken to mean This work is rushed. I said,
I get the feeling that Web Components seems a specification that
seems really pushed/rushed,
by that I meant it seemed as if the current spec is being pushed as
fast as possible toward standardization.
On Oct 7, 2013, at 12:24 PM, Rafael Weinstein rafa...@google.com wrote:
On Mon, Oct 7, 2013 at 3:24 AM, James Graham ja...@hoppipolla.co.uk wrote:
On 06/10/13 17:25, Dimitri Glazkov wrote:
And, if the script is executed against the global/window object of
the main document, can and
On Tue, Dec 3, 2013 at 7:03 PM, Ryosuke Niwa rn...@apple.com wrote:
On Oct 7, 2013, at 12:24 PM, Rafael Weinstein rafa...@google.com wrote:
On Mon, Oct 7, 2013 at 3:24 AM, James Graham ja...@hoppipolla.co.ukwrote:
On 06/10/13 17:25, Dimitri Glazkov wrote:
And, if the script is
On Dec 3, 2013, at 8:02 PM, Eric Bidelman ericbidel...@google.com wrote:
On Tue, Dec 3, 2013 at 7:03 PM, Ryosuke Niwa rn...@apple.com wrote:
On Oct 9, 2013, at 10:42 AM, Scott Miles sjmi...@google.com wrote:
On Mon, Oct 7, 2013 at 3:24 AM, James Graham ja...@hoppipolla.co.uk wrote:
On
On Sun, Oct 6, 2013 at 9:38 AM, Dimitri Glazkov dglaz...@chromium.org wrote:
So you have link href=blah.html in meh.html and blah.html is:
div id=test/div
script /* how do I get to #test? */ /script
document.currentScript.ownerDocument.querySelector(#test) :)
This only works for code running
they'll have to use a closure to capture the document that the template
lives in
Yes, this is true. But stamping of templates tends to be something custom
elements are really good at, so this paritcular use case doesn't come up
very often.
Out of curiosity, what have the Polymer guys been
I remember Adam raving about HTML Imports being awesome after he tried
them. Adam, can you provide color? :)
:DG
On Fri, Oct 18, 2013 at 4:11 PM, Scott Miles sjmi...@google.com wrote:
they'll have to use a closure to capture the document that the template
lives in
Yes, this is true. But
On Mon, Oct 7, 2013 at 3:24 AM, James Graham ja...@hoppipolla.co.uk wrote:
On 06/10/13 17:25, Dimitri Glazkov wrote:
And, if the script is executed against the global/window object of
the main document, can and should you be able to access the imported
document?
You can and
On Thu, Oct 10, 2013 at 2:42 AM, Scott Miles sjmi...@google.com wrote:
On Mon, Oct 7, 2013 at 3:24 AM, James Graham ja...@hoppipolla.co.ukwrote:
On 06/10/13 17:25, Dimitri Glazkov wrote:
And, if the script is executed against the global/window object of
the main document, can and
On 06/10/13 17:25, Dimitri Glazkov wrote:
And, if the script is executed against the global/window object of
the main document, can and should you be able to access the imported
document?
You can and you should. HTML Imports are effectively #include for the Web.
Yes, that sounds
On Mon, Oct 7, 2013 at 3:24 AM, James Graham ja...@hoppipolla.co.uk wrote:
On 06/10/13 17:25, Dimitri Glazkov wrote:
And, if the script is executed against the global/window object of
the main document, can and should you be able to access the imported
document?
You can and
So, Anne just reopened this bug:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22305
To bring in the discussion here and provide some context, a bunch of us got
together at the Mozilla Summit in Brussels to discuss the current state of
web components so that we could figure out what platform
On Sun, Oct 6, 2013 at 6:26 AM, Angelina Fabbro angelinafab...@gmail.comwrote:
So, Anne just reopened this bug:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=22305
To bring in the discussion here and provide some context, a bunch of us
got together at the Mozilla Summit in Brussels to
On Sun, Oct 6, 2013 at 5:25 PM, Dimitri Glazkov dglaz...@chromium.org wrote:
On Sun, Oct 6, 2013 at 6:26 AM, Angelina Fabbro angelinafab...@gmail.com
wrote:
And, if the script is executed against the global/window object of the
main document, can and should you be able to access the imported
On Sun, Oct 6, 2013 at 9:21 AM, Anne van Kesteren ann...@annevk.nl wrote:
On Sun, Oct 6, 2013 at 5:25 PM, Dimitri Glazkov dglaz...@chromium.org
wrote:
On Sun, Oct 6, 2013 at 6:26 AM, Angelina Fabbro
angelinafab...@gmail.com
wrote:
And, if the script is executed against the global/window
We should ask Polymer people: they wrote a ton of code with Imports now
and I bet they have opinions.
The Polymer team has successfully adopted/evolved the modality Dimitri
describes. Imported documents work roughly as #includes, and
`currentScript.ownerDocument` is interrogated if one needs to
26 matches
Mail list logo
