W3C home > Mailing lists > Public > public-web-perf@w3.org > February 2013

[minutes] Web Performance WG Teleconference #98 2013-02-20

From: Jatinder Mann <jmann@microsoft.com>
Date: Wed, 20 Feb 2013 19:35:42 +0000
To: "'public-web-perf@w3.org'" <public-web-perf@w3.org>
Message-ID: <b8c63bd7aa9040178a3a48ced9e4f637@BLUPR03MB065.namprd03.prod.outlook.com>
Meeting Summary:



1.     Page Visibility to PR

The Page Visibility specification has been published as a Proposed Recommendation, http://www.w3.org/TR/2013/PR-page-visibility-20130219/. We expect to publish the Timing control for script-based animations spec to be published as CR in the next two weeks.



2.     Test Cases

James Simonsen will follow up and update the Intel submitted Resource Timing and User Timing test cases to ensure non-standard APIs have been removed, so the tests can be run in the W3C harness.



I will follow up on updating the Microsoft submitted requestAnimationFrame test case - the test is testing cancelRequestAnimationFrame, even though the name was changed to cancelAnimationFrame. Also, test cases testing the DOMHighResTimeStamp callback parameter are needed.



3.     Navigation Timing L2 Updates

Updates to Navigation Timing L2 to include prerender information have been made. The working group is interested in hearing whether there are additional attributes that should be added to this specification.



4.     Beacon API

Alois and I are working on a Beacon API spec that will give a clearer definition of our use cases and requirements. We can review this spec and decide then whether it makes sense to have a separate API or to rely on existing APIs. If we do rely on existing APIs, we need to consider whether the solution solves our problem and will not confuse developers and risk adoption.



We expect to have more specifications proposed in the upcoming weeks.




W3C Web Performance WG Teleconference #98 2013-02-20



IRC log: http://www.w3.org/2013/02/20-webperf-irc



Meeting Minutes: http://www.w3.org/2013/02/20-webperf-minutes.html



Attendees

Jatinder Mann, James Simonsen, Philippe Le Hegaret, Arvind Jain, Ganesh Rao, Rob Dickenson


Scribe

Jatinder Mann



Agenda

1.     Discuss Test Cases issues

2.     Feedback on Existing Specifications

3.     Feedback on New Specifications

--------------------------------------------------------------------------------



Minutes:
Page Visibility to PR

Jatinder: When do we expect that rAF be moved to CR?

Philippe: There are a few threads that I have to close on. Probably will take two weeks before rAF moves to CR.
Test Cases

Jatinder: I can't seem to get Intel's Resource Timing test cases to run in IE10. They don't return a pass or fail. I'll email Pan.
Navigation Timing L2 Updates

Jatinder: I added prerenderSwitch attribute to the Navigation Timing L2 spec. See mailing list discussion: http://lists.w3.org/Archives/Public/public-web-perf/2013Feb/0048.html.

https://dvcs.w3.org/hg/webperf/raw-file/tip/specs/NavigationTiming2/Overview.html
Beacon API

Jatinder: Alois and I have followed up with the Web Apps working group. To us it appears that writing an initial draft of a Beacon API will help us get a clearer definition of what we need, rather than starting to see how it fits into existing specs. Having this initial spec it will be also easier to decide about the actual fit into XHR or other APIs.
... I'm working on a spec now.

Arvind: I've some experience doing this use case. One we could look at ping and see if it works.

Jatinder: Can you point me to the ping spec?

Arvind: I believe it is a part of the HTML5 spec.

<plh> http://www.w3.org/TR/CSP/#report-uri

Plh: Ping was rejected by the HTML5 WG, but it's a part of the WhatWG. There were concerns of privacy.

Arvind: I can also help put together some use cases for the Beacon API.

<plh> http://lists.w3.org/Archives/Public/public-web-perf/2012Oct/0017.html

Jatinder: I recommend we talk about uses cases for Beacon API, next week.

<plh> http://lists.w3.org/Archives/Public/public-web-perf/2012Oct/0023.html

Arvind: Back to Navigation Timing, I think we should ask for more ideas to include in the Navigation Timing. We should probably reach out to the working group.

Jatinder: We should have a few new specs to discuss in the next week.
Test Cases

Jatinder: I had mentioned that Resource Test cases do not work in IE right now. James, Ganesh, comments?

http://w3c-test.org/webperf/tests/submission/Microsoft/requestAnimationFrame/test_paint.htm

James: I believe the bugs that you filed on User Timing is probably occurring on Resource Timing as well. I'll look into this.

<simonjam> webkit raf tests: http://trac.webkit.org/browser/trunk/LayoutTests/fast/animation

Plh: We only have one requestAnimationFrame test.

Jatinder: That test has a few bugs, cancelRequestAnimationFrame name has changed, there no testing of the DOMHighResTimeStamp. I'll see if I can get this updated.

James: I'll provide more webkit tests as well.
Charter

Plh: I'll send the charter to AC reps for approval.
... I know that Akamai is planning on joining the working group, including other folks.

<plh> http://www.w3.org/2013/01/webperf.html
Received on Wednesday, 20 February 2013 19:37:29 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 20 February 2013 19:37:29 GMT