Web Performance Working Group, I'm looking at you specifically.
-
-
Replying to @really_bz @bz_moz
Feel free to ping me anywhere with a bit of context and I'll follow up for you. Filed https://github.com/w3c/navigation-timing/issues/63 … on them today.
2 replies 0 retweets 0 likes -
I wish
@igrigorik would make it a bit more of a priority. There’s similar issues with undefined caches for rel=preload and friends.1 reply 0 retweets 1 like -
Replying to @annevk
the undefined caches go beyond preload. Agree they need to be defined. On my (admittedly crowded) TODO list /
@bz_moz@igrigorik1 reply 0 retweets 1 like -
Anne: believe me, it's not for the lack of interest.. there's only so many hours in a day.
1 reply 0 retweets 2 likes -
I think the balance between increasing and reducing technical debt has been off.
2 replies 0 retweets 1 like -
my main focus across our L2's has been to rationalize/unify concepts and layering across the previous (L1) specs /cc
@toddreifsteck2 replies 0 retweets 0 likes -
Replying to @igrigorik @annevk and
you're right though, there is a mountain of integration (Fetch, HTML) work still to be done—that's the next chunk big of work..
2 replies 0 retweets 0 likes -
Replying to @igrigorik @annevk and
Just to be clear, those are NOT the issues that led me to give up on the webperf working group. The fundamental approach to specs did.
1 reply 0 retweets 0 likes -
Replying to @really_bz @bz_moz and
we've been chipping away at the plan we defined in: https://lists.w3.org/Archives/Public/public-web-perf/2015Jun/thread.html#msg96 …, 10k-foot view: https://docs.google.com/document/d/1ZKW9N0cteHgK91SyYQONFuy2ZW6J4Oak398niTo232E/edit …
2 replies 0 retweets 0 likes
Chipping away for almost 2 years now. Hardly been a priority, has it? And even that plan is not that great.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.