forked from bvaughn/scheduling-profiler-prototype
-
Notifications
You must be signed in to change notification settings - Fork 0
Add Firefox support #52
Copy link
Copy link
Open
Labels
importance: 2 - should haveThis should be implemented, but we will still have a working product if we don'tThis should be implemented, but we will still have a working product if we don'tphase: 2 - iterationIterations on our MVPIterations on our MVPurgency: 4 - no urgencyWe have an indefinite amount of time to complete thisWe have an indefinite amount of time to complete thiswork type: implementationA task that primarily involves bashing codeA task that primarily involves bashing codework type: investigationA task that primarily involves digging into a particular problemA task that primarily involves digging into a particular problem
Metadata
Metadata
Assignees
Labels
importance: 2 - should haveThis should be implemented, but we will still have a working product if we don'tThis should be implemented, but we will still have a working product if we don'tphase: 2 - iterationIterations on our MVPIterations on our MVPurgency: 4 - no urgencyWe have an indefinite amount of time to complete thisWe have an indefinite amount of time to complete thiswork type: implementationA task that primarily involves bashing codeA task that primarily involves bashing codework type: investigationA task that primarily involves digging into a particular problemA task that primarily involves digging into a particular problem
Speedscope should already have support for Firefox. We'll need to update our preprocessing code to ingest Firefox profiles, and likely also remove our dependence on
TimelineEventthroughout the app as that appears to be a Chrome concept.