<trackbot> Date: 11 February 2015
Ilya: I'm making progress on feedback
... looking for feeback on removing naigation
... embedded case is missing
... if we remove navigation restriction, it becomes pretty simple
Yoav: I think the use case is useful
... concern is security
... should we expose it?
... need to get security folks involved
Ilya: we wouldn't be reporting info that would have been reported if it had been succesful
... but third party reports are more problematic
... third.com has a resource, someone tries to load on a different site. That should be fine to report
Yoav: notifying the embeder might be problematic
Ilya: right. maybe opt-in policy
Todd: still thinking it through
Tobin: do we have an idea of the clear scenarios?
Ilya: no, we have an example section
... but we could add it
... that's good idea
... I'll folllow with a new draf
Plh: changing the type of PerformanceEntryList is problematic
... right now, it's an array
... forEach, map, filter, etc
... we would remove those functions otherwise
interface PerformanceEntryList {
getter PerformanceEntry item(unsigned long index);
readonly attribute unsigned long length;
PerformanceEntryList getEntriesByName(name);
}
Plh: I'll follow up on the list
... otherwise, proposal looks fine
Tobin: I like the idea
... better object model for mass events
... will keep thinking about it
??: in general, high level is looking good
Yoav: looks good
... was wondering about the possibility of allocating more
... but other than that, it's fine
... looks useful as well
... why 150 limit?
Ilya: copied from resource timing
... we could change it
Yoav: why not start higher?
[...]
Yoav: ok, makes sense
Resolved: Server Timing is published as FPWD
Plh: can't we remove SYNTAX_ERR limitation?
Ilya: don't see any reason why not
Plh: negative duration restriction...
[back and forth around whether negative values are useful]
??: given the scenario in the email, it sounds legitimate
Todd: I'll test it in IE
plh: Why can't we get performance.getEntriesByType("navigation") implemented?
<scribe> ACTION: plh to send an email about what's new in navtiming2 [recorded in http://www.w3.org/2015/02/11-webperf-minutes.html#action01]
<trackbot> Created ACTION-150 - Send an email about what's new in navtiming2 [on Philippe Le Hégaret - due 2015-02-18].
Ilya: we also redirect handling for R and NT
<scribe> ACTION: plh to send an email on RAF [recorded in http://www.w3.org/2015/02/11-webperf-minutes.html#action02]
<trackbot> Created ACTION-151 - Send an email on raf [on Philippe Le Hégaret - due 2015-02-18].
plh: can we allow editors to publish in /TR if the editor is willing to send email to the list?
Resolved: Editors are allowed to update WD in /TR
Ilya: service workers wants to have access to window.performance, RT and UT
... needs to update the spec to not specifically call out window
??: could that be addressed by performance observers?
Ilya: that's different
... I'll take a look at it
<scribe> ACTION: plh to make it clear that duration can be negative in UT [recorded in http://www.w3.org/2015/02/11-webperf-minutes.html#action03]
<trackbot> Created ACTION-152 - Make it clear that duration can be negative in ut [on Philippe Le Hégaret - due 2015-02-18].