- From: Eli Perelman <eperelman@mozilla.com>
- Date: Tue, 31 Oct 2017 16:14:25 +0000
- To: Timothy Dresser <tdresser@chromium.org>
- Cc: public-web-perf@w3.org
Received on Tuesday, 31 October 2017 16:15:00 UTC
For posterity [1], here is the definition of "contentInteractive" that we adopted within Firefox OS: "Emit this marker when your application designates that it has bound the events for the minimum set of functionality to allow the user to interact with the "above-the-fold" content made available at visuallyLoaded." Granted, this mark was implied, not inferred. Eli Perelman Mozilla [1] https://developer.mozilla.org/en-US/docs/Archive/B2G_OS/Developing_Gaia/Raptor/Responsiveness_guidelines On Tue, Oct 31, 2017 at 11:01 AM Timothy Dresser <tdresser@chromium.org> wrote: > As discussed in our last meeting, here > <https://docs.google.com/document/d/1l50v3ljDeUmj9qBsfdPc3wKe_1CY5KFYI1baye2NhYk/edit?ts=59dfaf65#>'s > a description of Chrome's current implementation of Time to Interactive. > > Here > <https://docs.google.com/document/d/1y6NYcI2NyLMh88KVr2NaevdX2e-e03vL99Wn-gy_hVk/edit#>'s > some rough brainstorming on the next step for Chrome's implementation. > > At TPAC, we're hoping to discuss: > > - The high level objective of TTI. > - Chrome's current algorithm for computing TTI. > - Enabling TTI measurement in the wild. > > Tim >
Received on Tuesday, 31 October 2017 16:15:00 UTC