See also: IRC log
<trackbot> Date: 01 April 2015
https://w3c.github.io/charter-webperf/
plh: pay attention to section 2
ilya: how do we say that we want to revisit some of the old specs?
plh: we can make a general statement in that sense
ilya: do you guys see anything missing?
yoav: things that were discussed
at the velocity summit
... visibility observers
... not sure we have the answer yet
... or something in that range
todd: in scope of page visibility?
ilya: seems beyond PV, and we
have frame timing
... other things that should be on the list? please open issues
in the repo
plh: should strike the sentence on member only list
todd: we have prefetch in
html5
... then prerender, preload, etc.
... preload was targeted to solve many of them
... should we focus preload?
... even on prefetch, the wording is vague
... should we pull it in?
ilya: look into issues on
preloading
... don't think there are concerns to use
prefetch/prerender
... initial reason was inconsistency between browsers
... but we could make them better
... I'm ok with going back to those
yoav: totally behind that
... future friendliness argument seems the best option
... ok to go back to prefetch/prerender
ilya: will update resource
hints
... refine preconnect/prefetch/prerender
... that will simplify a lot of things
http://microformats.org/wiki/rel-prerender
todd: already pulled travis with
this
... his take was that we should update the html spec or pull it
from it
ilya: I prefer separate
spec
... but we'll need the right hooks
<igrigorik> https://github.com/w3c/preload/pull/15
<igrigorik> https://github.com/w3c/preload/pull/16
Ilya: preload/#15 makes as
attribute mandatory
... feedback from intent to implement that it opens interested
side effect
... this will also simplify the processing
Yoav: I like it because missing
'as' would be a common authoring mistake
... if it resolves in a priority change, that would be
difficult to detect
... so ignoring the hint is absent is better imho
Todd: by forcing the user to make the choice, we avoid the authoring issue. right?
Ilya: correct
... if somebody specified an invalid context, we shouldn't
initiate the request
... friendly warning and ignore
... like an invalid link tag
yoav: separate issue: are we
doing sync or async fetch request?
... if we're building the link dynamically, we don't want to
create a situation when the img gets invalidated because of
order
ilya: preload/#16 is supposed to address that
yoav: what happens if as is
changed dynamically?
... do we re-apply CSP
ilya: doesn't affect CSP
... but it may reprioritize the resource
... I'll update the language for #15
... then merge
todd: setting the link and the as might cause issue?
yoav: let's merge and figure out corner cases
ilya: I'll merge #16
yoav: I have an issue related to
media attribute and viewport setting
... concern is that allowing resources to be preloaded based on
media attribute, in some cases, we don't know the actuall
viewport dimension when we're fetching the resources
ilya: can we set the viewport via header?
yoav: not as a meta
... I don't think we should do this
... viewport should be saner
... discussion on blink-dev didn't go very far
... @viewport is over engineered
... it's possible for authors to shoot themselves in the
foot
ilya: please open a bug
yoav: will do
... as well as sync question
todd: performance observers to performance timeline
https://github.com/w3c/performance-timeline/pull/8
Ilya: I need to update the
PR
... current performance observers provide a callback
https://lists.w3.org/Archives/Public/public-web-perf/2015Feb/0045.html
https://lists.w3.org/Archives/Public/public-web-perf/2015Feb/0030.html
[...]
<igrigorik> https://github.com/w3c/navigation-timing/pull/10
<ToddReifsteck> https://github.com/w3c/navigation-timing/pull/10/files
<ToddReifsteck> https://github.com/w3c/resource-timing/pull/18
<igrigorik> new version: https://cdn.rawgit.com/w3c/navigation-timing/move-perf-interface-definition/index.html
todd: number of usages are
increasing
... 1.7% usage
<igrigorik> plh: see above for readable version of https://github.com/w3c/navigation-timing/blob/move-perf-interface-definition/index.html
todd: it's existence stats
plh: any browser counter stats?
todd: could pull that in a month
https://lists.w3.org/Archives/Public/public-web-perf/2013Aug/0051.html
plh: would be helpful to go back to those threads before recycling again
yoav: blink-dev resistance based
on implementations and fear of abuse
... would be useful to summarize
todd: would be valuable to have a
few customers that have use cases
... where there is gain
<scribe> ACTION: Todd to come back with data related to setImmediate [recorded in http://www.w3.org/2015/04/01-webperf-minutes.html#action01]
<trackbot> Created ACTION-155 - Come back with data related to setimmediate [on Todd Reifsteck - due 2015-04-08].
zaki, close agendum 5
https://github.com/w3c/performance-timeline/pull/9
ilya: would it make to define a
more general concept:
getEntriesThatHaveThisAttributeOrProperty
... so that we can annotate our entries in the futre
todd: makes a lot of sense
... will have to talk to developers on implementations
plh: how far to go in phrasing the question?
ilya: I'll write some use cases
for it
... it does open a lot of possibilities
... to push more records
This is scribe.perl Revision: 1.140 of Date: 2014-11-06 18:16:30 Check for newer version at http://dev.w3.org/cvsweb/~checkout~/2002/scribe/ Guessing input format: RRSAgent_Text_Format (score 1.00) No ScribeNick specified. Guessing ScribeNick: plh Inferring Scribes: plh Default Present: [Microsoft], +33.1.56.69.aaaa, Plh, +657888aabb, yoav, Ilya, +1.310.310.aacc, mbp Present: [Microsoft] +33.1.56.69.aaaa Plh +657888aabb yoav Ilya +1.310.310.aacc mbp Agenda: https://lists.w3.org/Archives/Public/public-web-perf/2015Mar/0046.html WARNING: No meeting chair found! You should specify the meeting chair like this: <dbooth> Chair: dbooth Found Date: 01 Apr 2015 Guessing minutes URL: http://www.w3.org/2015/04/01-webperf-minutes.html People with action items: todd[End of scribe.perl diagnostic output]