ISSUE-57: Browser Graphics Performance Testing

Browser Graphics Performance Testing

State:

CLOSED

Product:

testing

Raised by:

Giuseppe Pascale

Opened on:

2013-03-27

Description:

also available on the wiki:

http://www.w3.org/2011/webtv/wiki/Testing/Web_%26_TV_Testing_Discussions/performance_testing#Use_Case:_Browser_Graphics_Performance_Testing
------

Description:
Enable benchmarking of graphics relates specifications e.g. CSS Transition, Animation or Transform is important for devices with limited capability (like TV-sets and STBs).

Support from the user agent to extract relevant metric may be needed.


Motivation:
Functional testing of specifications like CSS Transform, Transition and Animation is not enough since the usability of such functionalities is heavily dependent on the browser capability of rendering the related graphic operations with acceptable performances. Being able to test such performances is then a key factor, expecially when dealing with devices with limited hw capability.


Dependencies:
As User Agent support may be required, discussion with relevant W3C WGs (e.g. WebPerf) may be required


What needs to be standardized:
The user agent may need to expose to Javascript metrics that can be used for benchmarking purposes.

One example is the mozilla window.mozPaintCount https://developer.mozilla.org/en-US/docs/DOM/window.mozPaintCount

Related discussion on a similar property for chromium is still open with no conclusion: http://code.google.com/p/chromium/issues/detail?id=65348 http://code.google.com/p/chromium/issues/detail?id=120796

Related Actions Items:

No related actions

Related emails:

1. webtv-ISSUE-57: Browser Graphics Performance Testing [testing] (from sysbot+tracker@w3.org on 2013-03-27)

Related notes:

Display change log