Oh I see. Thanks for the clarification.
On Thu, Oct 24, 2013 at 5:54 PM, Anne van Kesteren wrote:
> On Thu, Oct 24, 2013 at 1:38 AM, Hajime Morrita
> wrote:
> > OK, I will refer the fetch section in HTML spec then.
>
> I think you misunderstood, http://fetch.spec.whatwg.org/#fetching is
> the
On Thu, Oct 24, 2013 at 1:38 AM, Hajime Morrita wrote:
> OK, I will refer the fetch section in HTML spec then.
I think you misunderstood, http://fetch.spec.whatwg.org/#fetching is
the entry point.
--
http://annevankesteren.nl/
OK, I will refer the fetch section in HTML spec then.
On Wed, Oct 23, 2013 at 9:29 PM, Anne van Kesteren wrote:
> On Wed, Oct 23, 2013 at 1:16 PM, Hajime Morrita
> wrote:
> > I've been trying to define the import loading behavior on top of the
> "basic
> > fetch" algorithm of the fetch standa
On Wed, Oct 23, 2013 at 1:16 PM, Hajime Morrita wrote:
> I've been trying to define the import loading behavior on top of the "basic
> fetch" algorithm of the fetch standard. So feedback like yours are really
> appreciated.
"basic fetch" is not an entry point. It's an internal algorithm. You
shou
Hi Joe,
Thanks for trying HTML Imports and looking into the spec!
It's a spec bug. The intention of the spec is to allow CORS-aware cross
origin resources. It seems that something wrong happened during editing. I
filed a bug [1] for revising it.
I've been trying to define the import loading beha
Hi
I'm experimenting with HTML Imports to simplify a collection of
complicated web-apps. I'm really impressed with the functionality -
it's greatly simplified things. I'm currently using a polyfill but
looking forward to being able to use this natively.
I've hit a limitation though - I'd really l
