On Tue, Feb 24, 2015 at 9:32 AM, Brendan Long s...@brendanlong.com wrote:
HTTP/2 associates priority information with HEADERS
http://http2.github.io/http2-spec/#HEADERS (but as a flag, not as a
normal header), so maybe it would make sense to add this to Fetch's
Headers
For anyone interested in this topic.. Note that the conversation has moved
to Bugzilla, please chime in with your thoughts and feedback there:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27303#c14
On Tue, Nov 11, 2014 at 10:17 AM, Ilya Grigorik igrigo...@gmail.com wrote:
I've opened a bug
I've opened a bug to track this:
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27304
On Tue, Nov 4, 2014 at 4:44 PM, Ilya Grigorik igrigo...@gmail.com wrote:
On Wed, Nov 5, 2014 at 9:08 AM, Ryosuke Niwa rn...@apple.com wrote:
Re, re-evaluation previous elements: note that UA *can*, just
On Sat, Nov 1, 2014 at 5:18 PM, Simon Pieters sim...@opera.com wrote:
A bare link or style in body means that you have to re-evaluate
previous elements. With scoped you don't have to do that. IIRC this was
the
main reason for the current authoring requirements in the spec.
Without looking
On Wed, Nov 5, 2014 at 9:08 AM, Ryosuke Niwa rn...@apple.com wrote:
Re, re-evaluation previous elements: note that UA *can*, just as it does
today (modulo some error conditions), hold painting until it finds all
the
stylesheets, regardless of the link position in the document. So,
the (already) implemented
patterns both in markup and in some rendering engines... a simple update
that could pay high perf dividends.
ig
On Wed, Oct 29, 2014 at 2:46 PM, Ilya Grigorik igrigo...@gmail.com
wrote:
(based on discussion at the webperf group meeting at TPAC... hopefully I
On Thu, Oct 30, 2014 at 2:44 PM, Ben Maurer ben.mau...@gmail.com wrote:
On Thu, Oct 30, 2014 at 2:26 PM, Ilya Grigorik igrigo...@gmail.com
wrote:
On Thu, Oct 30, 2014 at 12:17 PM, Ben Maurer ben.mau...@gmail.com
wrote:
We talked a bit before about the idea of async stylesheets (like async
On Thu, Oct 30, 2014 at 7:56 AM, Simon Pieters sim...@opera.com wrote:
The spec currently allows style scroped@import other.css;/style in
body (at least at the start of an element). I don't know if it has the
properties you want in existing impls. I also don't know if scoped is OK or
not for
(based on discussion at the webperf group meeting at TPAC... hopefully I
captured the discussion correctly. If not, please jump in!)
HTML5 spec: If the rel attribute is used, the element is restricted to the
head element. [1]
Above language is too restrictive, allowing link element to be present
On Wed, Oct 8, 2014 at 11:36 AM, Peter Lepeska bizzbys...@gmail.com wrote:
Does this have implications for resource hints? Do we want the ability to
specify “noreferrer” for prerendered pages? Currently noreferrer only
applies to the a tag.
My understanding is that you set a global policy,
On Tue, Oct 7, 2014 at 8:28 AM, Peter Lepeska bizzbys...@gmail.com wrote:
Looks like this is already supported:
https://html.spec.whatwg.org/multipage/semantics.html#link-type-noreferrer
.
Just need to educate web developers to you use it.
It's a bit more complicated. The redirector use
On Thu, Sep 11, 2014 at 7:55 PM, Ryosuke Niwa rn...@apple.com wrote:
On Sep 8, 2014, at 10:54 PM, Ilya Grigorik igrigo...@gmail.com wrote:
On Mon, Sep 8, 2014 at 7:59 PM, Ian Hickson i...@hixie.ch wrote:
The platform is missing a lower-level primitive (declarative and
imperative
0-7 priority is not sufficient. See previous discussion / proposal:
http://lists.w3.org/Archives/Public/public-whatwg-archive/2014Aug/0081.html
ig
On Wed, Oct 1, 2014 at 10:54 AM, Chad Austin caus...@gmail.com wrote:
Hi all,
I posted the following message to WebApps, but Anne van Kesteren
On Wed, Oct 1, 2014 at 4:48 PM, Chad Austin caus...@gmail.com wrote:
Does HTTP 2.0's dependency graph + weights system allow traditional
priority semantics? That is, higher-priority resources would be serviced
before lower-priority resources, unless resource capacity remains available.
Yes,
On Wed, Oct 1, 2014 at 7:59 PM, Chad Austin caus...@gmail.com wrote:
I don't see a way to set a priority value in there. The specific wording
is Streams can be prioritized by marking them as dependent on the,
completion of other streams.
I see that a client can specify the weight of a
the same level of the tree, and based on assigned
weights within that level.
ig
On Wed, Oct 1, 2014 at 8:19 PM, Ilya Grigorik igrigo...@gmail.com wrote:
On Wed, Oct 1, 2014 at 7:59 PM, Chad Austin caus...@gmail.com wrote:
I don't see a way to set a priority value in there. The specific
On Mon, Sep 8, 2014 at 1:33 PM, Ian Hickson i...@hixie.ch wrote:
I really like your proposal for as=... Concretely it could look
something
like this:
link rel=preload
href=/some/asset.css
as=stylesheet(used to initialize default priority, headers,
etc)
On Mon, Sep 8, 2014 at 7:59 PM, Ian Hickson i...@hixie.ch wrote:
The platform is missing a lower-level primitive (declarative and
imperative) that is able to explain resource loading with the same
expressive power as requests initiated by the browser itself.
That isn't a problem.
I
[[stuck in the mod queue.. attempt #5, apologies for dupes if you get them]]
Ian, thanks for writing this up.
The first thing that strikes me about this entire topic is its scope, and
I'm wondering if we should take a step back and (a) extract some lower
level primitives, (b) leave the rest to
On Fri, Aug 15, 2014 at 9:26 AM, Ian Hickson i...@hixie.ch 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
(followup / continuation of [1])
Trying to hash out some ideas for how to connect Fetch and the new
transport capabilities of HTTP/2. Would love to hear everyone's thoughts:
https://docs.google.com/document/d/1jSpWc6jkrUoYtGWcxev9Blkkv9RhoO1XtqinBvXqhgY/edit
ig
[1]
On Mon, Aug 11, 2014 at 8:33 AM, Ian Hickson i...@hixie.ch 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
On Mon, Aug 11, 2014 at 12:57 PM, Ian Hickson i...@hixie.ch 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),
I'm working on the resource hints spec we've been discussing on
public-webperf...
This specification defines preconnect, preload, and prerender hints that
the developer, or the server generating or delivering the resources, can
use in an interoperable way to assist the user agent in the decision
, defining a do not execute bit on every
element seems painful. I'd rather have a fetch layer, and then just inject
the tag that would consume the fetched response and execute it when
injected -- seems cleaner.
ig
On Thu, Aug 7, 2014 at 2:04 PM, Ilya Grigorik igrigo...@gmail.com wrote:
I'm
On Thu, Aug 7, 2014 at 4:39 PM, Ben Maurer ben.mau...@gmail.com wrote:
On Thu, Aug 7, 2014 at 3:21 PM, Ilya Grigorik igrigo...@gmail.com wrote:
It would be nice if there was a more declarative relationship between the
declarative fetch and the eventual use of the resource (assuming
On Mon, Nov 18, 2013 at 8:13 PM, Bruno Racineux br...@hexanet.net wrote:
Because these (only 0.2% uzing gzip) stats do not look good at all in
support of your theoretical argument:
http://trends.builtwith.com/Server/GZIP-Module
That measures mod_gzip adoption.
HTTP Archive tracks top 300K
On Sun, Nov 10, 2013 at 12:58 PM, Adam Barth w...@adambarth.com wrote:
I believe you're applying an inappropriately high standard of required
agreement to this proposal, compared to what the usual required level
is for something to be accepted.
If Blink ships src-N and WebKit ships
On Sat, Nov 9, 2013 at 2:49 AM, Markus Lanthaler
markus.lantha...@gmx.netwrote:
Well, an alternative would be to move the complexity to the server. I very
much doubt that webmasters are going to create all those variations
manually
anyway. And if so, it's enough to store them according a
29 matches
Mail list logo
