W3C

- DRAFT -

Web Performance Working Group Teleconference

21 Aug 2013

See also: IRC log

Attendees

Present
Daniel, [Microsoft], Plh, +1.949.754.aaaa, +1.408.203.aabb, Rob, Arvind, +1.650.214.aacc, +1.650.214.aadd, +1.503.712.aaee, +1.650.214.aaff, JatinderMann, plh, AaronHeady, ArvindJain, RobDickenson
Regrets
Chair
SV_MEETING_CHAIR
Scribe
JatinderMann

Contents


<trackbot> Date: 21 August 2013

Element Visibility

Arvind: I've seen a few different types of requests: one is to see visibility on an element level. Today visibility is for top level browsing context. One ask is to see if it can be made at an element level. E.g., if an iframe is scrolled below the fold, it wants to know if its visible or not.
... In one case the JavaScript on the main page can query the visibility of elements. The other case is third party advertisers want to be able to query when their ad is viewed or not.
... Mozilla has a interface to give the iframe the screen coordinates to determine screen coordinates. See https://www.w3.org/Bugs/Public/show_bug.cgi?id=22931.

Jatinder: If we are giving screen coordinates, we can just do the math and avoid the developer doing the math.
... Let's put together an Element Visibility to answer the first part of the question. I'll share a draft with you Arvind. Arvind, also send me any thoughts or proposals.
... We need to determine whether Chrome or IE for cross origin iframes share the top level parent or not.

Arvind: I'll follow up with Chrome behavior.

Jatinder: I can follow up with IE behavior.

Resource Priorities

<plh> http://www.w3.org/2013/08/results-user-timing-tests.html

Jatinder: Please review the Resource Priorities spec updates and raise issues. Thanks!

Test Cases

Plh: IE and Chrome both pass the tests.

<plh> http://www.w3.org/2013/08/results-google-resource-timing-tests.html

Plh: Do we need any additional tests?

James: I don't believe there are new tests we need to write.

Plh: Jatinder, can you check for the IE test failures?

Jatinder: I'll review all the test cases. I think this is a good opportunity to find test case issues, browser issues, or potentially spec issues.

Plh: I think we can move User Timing and Performance Timeline to PR and rAF to CR, based on this information. Resource Timing will just have to come in after.

Next meeting

James: I'm out next week.

Plh: Me too.

Jatinder: Let's schedule our next meeting for two weeks out.

Summary of Action Items

[End of minutes]

Minutes formatted by David Booth's scribe.perl version 1.138 (CVS log)
$Date: 2013-08-21 18:04:16 $

Scribe.perl diagnostic output

[Delete this section before finalizing the minutes.]
This is scribe.perl Revision: 1.138  of Date: 2013-04-25 13:59:11  
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: JatinderMann
Inferring Scribes: JatinderMann
Default Present: Daniel, [Microsoft], Plh, +1.949.754.aaaa, +1.408.203.aabb, Rob, Arvind, +1.650.214.aacc, +1.650.214.aadd, +1.503.712.aaee, +1.650.214.aaff
Present: Daniel [Microsoft] Plh +1.949.754.aaaa +1.408.203.aabb Rob Arvind +1.650.214.aacc +1.650.214.aadd +1.503.712.aaee +1.650.214.aaff JatinderMann plh AaronHeady ArvindJain RobDickenson

WARNING: No meeting chair found!
You should specify the meeting chair like this:
<dbooth> Chair: dbooth

Found Date: 21 Aug 2013
Guessing minutes URL: http://www.w3.org/2013/08/21-webperf-minutes.html
People with action items: 

[End of scribe.perl diagnostic output]