Add profiler for Oxide
Bug #1565280 reported by
Chris Coulson
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Oxide |
Triaged
|
Low
|
Unassigned |
Bug Description
chrome://profiler/ is part of Chrome rather than content. It would be nice to implement something similar in Oxide too
Changed in oxide: | |
status: | New → Triaged |
importance: | Undecided → Low |
To post a comment you must log in.
Does that mean it will go away as part of the upstream internal code
reshuffle?
On Sat, Apr 2, 2016 at 4:24 PM, Chris Coulson <email address hidden>
wrote:
> Public bug reported: /bugs.launchpad .net/bugs/ 1565280 /bugs.launchpad .net/oxide/ +bug/1565280/ +subscriptions /launchpad. net/~ubuntu- webapps- bugs /launchpad. net/~ubuntu- webapps- bugs /help.launchpad .net/ListHelp
>
> chrome://profiler/ is part of Chrome rather than content. It would be
> nice to implement something similar in Oxide too
>
> ** Affects: oxide
> Importance: Low
> Status: Triaged
>
> ** Changed in: oxide
> Status: New => Triaged
>
> ** Changed in: oxide
> Importance: Undecided => Low
>
> --
> You received this bug notification because you are a member of Ubuntu
> WebApps bug tracking, which is subscribed to Oxide.
> https:/
>
> Title:
> Add profiler for Oxide
>
> Status in Oxide:
> Triaged
>
> Bug description:
> chrome://profiler/ is part of Chrome rather than content. It would be
> nice to implement something similar in Oxide too
>
> To manage notifications about this bug go to:
> https:/
>
> --
> Mailing list: https:/
> Post to : <email address hidden>
> Unsubscribe : https:/
> More help : https:/
>