Closed Bug 1015384 Opened 6 years ago Closed 5 years ago

[Browser] Implement new startup loading events

Categories

(Firefox OS Graveyard :: Gaia::Browser, defect, P2)

ARM
Gonk (Firefox OS)
defect

Tracking

(Not tracked)

RESOLVED INVALID

People

(Reporter: Eli, Unassigned)

References

Details

(Keywords: perf, Whiteboard: [c=automation p= s= u=2.1])

+++ This bug was initially created as a clone of Bug #837668 +++

We need to measure when the app is usable by the user. For that we'll need to send an event (the moment is specific to the app) to |window| that the performance test will be able to receive.
Bug 996038 introduces new events outlining the phases of application startup. Each of these 5 events needs to be implemented.
Summary: [Browser] "ready to use" perf measurement → [Browser] Implement new startup loading events
As an FYI, this implementation needs to land in 2.0 as it is important for meeting release performance acceptance criteria.

https://wiki.mozilla.org/FirefoxOS/Performance/Release_Acceptance
FYI: Browser app instrumentation should be done for 2.1 rather than 2.0 per below:

----- Forwarded Message -----
From: "Kyle Machulis" <kmachulis@mozilla.com>
To: "dev-gaia" <dev-gaia@lists.mozilla.org>
Sent: Tuesday, August 5, 2014 8:14:36 PM
Subject: Please do not land any more changes to the old browser app

As of the end of this sprint, we are hoping to have the old browser app simply be a shell app that transfers data to various datastores and deletes itself. This is in preparation for system browser in v2.1.

Please do not make/land any more changes to the old browser app (the one in apps/browser). They will conflict with the changes of working on stripping out the old browser, and will be deleted in about a week anyways.
_______________________________________________
dev-gaia mailing list
dev-gaia@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-gaia
Whiteboard: [c=automation p= s= u=] → [c=automation p= s= u=2.1]
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.