From 260b55602dc114a9f40991712bc361fe4d906ef8 Mon Sep 17 00:00:00 2001 From: Philip Tellis Date: Wed, 2 May 2012 14:07:13 -0400 Subject: [PATCH] update use cases to include WebTiming case under normal case --- doc/use-cases.html | 18 ++++++++---------- 1 file changed, 8 insertions(+), 10 deletions(-) diff --git a/doc/use-cases.html b/doc/use-cases.html index 9a595137a..f50aad414 100644 --- a/doc/use-cases.html +++ b/doc/use-cases.html @@ -38,20 +38,18 @@

1. Measure a page's perceived performance.

  1. User clicks a link on a page we control and page is usable when onload fires
    + OR
    + User types in URL/clicks a bookmark or link on a page we don't control and our page is usable when onload fires and + the user is using a browser that supports the WebTiming + API (IE9+, Chrome, Firefox 7+).
    See HOWTO #1a.
  2. User clicks a link on a page we control and page is usable at some developer determined point
    + OR
    + User types in URL/clicks a bookmark or link on a page we don't control and our page is usable at some developer determined point and + the user is using a browser that supports the WebTiming + API (IE9+, Chrome, Firefox 7+), but not in other browsers.
    See HOWTO #1b.
    3. - -
  3. User types in URL/clicks a bookmark or link on a page we don't control and our page is usable when onload fires.
    - This is currently possible in browsers that support the WebTiming - API (eg: IE9), but not in other browsers.
    - See TODO #2.
    4. - -
  4. User types in URL/clicks a bookmark or link on a page we don't control and our page is usable at some developer determined point
    - This is currently possible in browsers that support the WebTiming - API (eg: IE9), but not in other browsers.
    - See TODO #2.