On Fri, 15 Aug 2014, Ilya Grigorik wrote:
>
> - rel='stylesheet'>
> - above stylesheet is "dynamic" and returns a pointer to a UA optimized
> font file that lives on https://fonts.gstatic.com
Ah, yeah, that's an excellent example. Thanks.
> That said, I think we're on the same page... I'm just
On Fri, Aug 15, 2014 at 9:26 AM, Ian Hickson wrote:
> > Two high-level cases:
> > (a) optimizing load sequence of page that's currently being loaded
> > (b) optimizing page load of a (potential) future navigation
> >
> > For (a), we need to expose "preconnect" and "preload", such that the
> > dev
On Mon, 11 Aug 2014, Ilya Grigorik wrote:
> On Mon, Aug 11, 2014 at 12:57 PM, Ian Hickson wrote:
> >
> > I hope to be able to post more concrete proposals soon, it's currently
> > blocked on my understanding how I should be integrating HTML with ES6.
>
> Any bugs or threads that I can follow to
On Mon, Aug 11, 2014 at 12:57 PM, Ian Hickson wrote:
> > It's murky to me how I'd declare a resource, specify its priority
> > relative to others, and/or add a dependency. Any other (more complete)
> > examples, by any chance? :)
>
> All of that is out of scope of ES6 (and thus the gliffy), but i
On Mon, 11 Aug 2014, Ilya Grigorik wrote:
>
> Will this result in API that extends beyond import and ES6 module use
> cases? For example, I want to have the building blocks that will allow
> me to declare these dependencies on my own: "these two images before
> that script, but after this styles
On Mon, Aug 11, 2014 at 8:33 AM, Ian Hickson wrote:
> On Thu, 7 Aug 2014, Ilya Grigorik wrote:
> >
> > I'm working on the "resource hints" spec we've been discussing on
> > public-webperf...
>
> FYI, I'm currently working an a dependency system update to HTML which has
> the goals of:
>
> - merg
On Thu, 7 Aug 2014, Ilya Grigorik wrote:
>
> I'm working on the "resource hints" spec we've been discussing on
> public-webperf...
FYI, I'm currently working an a dependency system update to HTML which has
the goals of:
- merging HTML import dependency management and ES6 module dependency
+1 to breaking the dependency between fetching the resource and how it is later
used in the document. This type of “late binding” enables many page
optimizations.
Peter
PS. My apologies if you’ve already seen a message saying similar. I’m not sure
if the mailing list is accepting my messages o
Sweet, I think we're on the same page. I completely agree with your high
level goal of a declarative fetch interface.
Agreed that matching is still critical, eg for the Link header use case.
On Thu, Aug 7, 2014 at 10:40 PM, Ilya Grigorik wrote:
>
>
>
> On Thu, Aug 7, 2014 at 4:39 PM, Ben Maure
On Thu, Aug 7, 2014 at 4:39 PM, Ben Maurer wrote:
>
> On Thu, Aug 7, 2014 at 3:21 PM, Ilya Grigorik wrote:
>
>>
>> It would be nice if there was a more declarative relationship between the
>>> declarative fetch and the eventual use of the resource (assuming the
>>> resources are on the same page)
On Thu, Aug 7, 2014 at 3:21 PM, Ilya Grigorik wrote:
>
> It would be nice if there was a more declarative relationship between the
>> declarative fetch and the eventual use of the resource (assuming the
>> resources are on the same page).
>>
>
> I would like to break that dependency. I want layer
On Thu, Aug 7, 2014 at 2:55 PM, Ben Maurer wrote:
> Not sure if you've seen this thread:
> http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2014-July/297257.html.
> I had the same basic interest as you (decoupling resource fetching from
> execution). I'd be curious to hear your thoughts about
Hey,
Not sure if you've seen this thread:
http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2014-July/297257.html.
I had the same basic interest as you (decoupling resource fetching from
execution). I'd be curious to hear your thoughts about that thread.
I really like the concept of a declarati
13 matches
Mail list logo
