public-web-perf@w3.org from May 2011 by subject

[agenda] Web Performance WG Teleconference #28 Agenda 2011-04-13

[agenda] Web Performance WG Teleconference #31 Agenda 2011-05-04

[agenda] Web Performance WG Teleconference #32 Agenda 2011-05-11

[agenda] Web Performance WG Teleconference #33 Agenda 2011-05-18

[agenda] Web Performance WG Teleconference #34 Agenda 2011-05-25

[AnimationRequestFrame] Initial editor's draft of AnimationRequestFrame spec available

[AnimationRequestFrame] Sample all animations operation and cancelRequestAnimationFrame specification updated

[minutes] 20110504 Web Performance WG Teleconference #31

[minutes] 20110511 Web Performance WG Teleconference #32

[minutes] 20110518 Web Performance WG Teleconference #33

[minutes] 20110525 Web Performance WG Teleconference #34

[NavigationTiming] incorrect description for requestStart

[Page Visibility] ACTION-26: Check whether to name the API window.visible, document.visible, window.pageVisible and document.pageVisible.

[Page Visibility] First Public Working Draft to be Published

[Page Visibility] Spec -- privacy concern

[Page Visibility] Spec Updates

[PageVisibility] event name

[PageVisibility] Feedback on example in the Page Visibility editor's draft April 27, 2011

[PageVisibility] location of the interface

[PageVisibility] specific visibility states

[RequestAnimationFrame] issue tracking

[RequestAnimationFrame] Spec rename + move

[Resource Timing] ACTION-33: Update spec to include a reference to what the expected behavior with plugins

[Resource Timing] Feedback on the IDL

[Resource Timing] Section 4.6 Processing Model

[Resource Timing] Spec Updates

[Resource Timing] User feedback and a modified proposal

[Resource/User Timing] Spec Updates

[ResourceTiming] initiator types

[ResourceTiming] Privacy

[ResourceTiming] Resource timing details

[User Timing] Spec updates

[UserTiming] Unifying marks and measures

Call for Exclusions: Resource Timing

FYI: First Draft of Resource Timing Published

ISSUE-1 (scheduling): Scheduling processing model needs to be more tightly defined [Request Animation Frame]

ISSUE-2 (callback-value): Callback time parameter needs definition [Request Animation Frame]

ISSUE-3 (monotonic-clock): Animation frame times should be monotonically increasing [Request Animation Frame]

ISSUE-4 (element-parameter): We perhaps should support an element parameter to requestAnimationFrame() [Request Animation Frame]

ISSUE-5 (target-rate): Expected callback rates should be documented [Request Animation Frame]

ISSUE-6: (duplicate callbacks): Spec needs to clarify expected behavior for duplicate calls of the same callback [Request Animation Frame]

Resource Timing - What's included

Simplified Resource Timing and User Timing

Last message date: Tuesday, 31 May 2011 20:40:35 UTC