Nazım Can Altınova
Nazım Can Altınova
Currently we compute CPU scores to determine which threads to make visible by default. We can also display that information in the thread selection popup to give our users more...
We decided to go with a different active tab view that's closer to the current view. So it doesn't make sense to keep that view in the source code anymore....
Currently we don't do any special ordering for the global tracks. So they are displayed as the same order as their order in the profile data. We already have a...
Currently we have a way to filter samples by their innerWIndowId. It's not working correctly (see #3236, #3367). Let's remove that code completely as we don't need it in the...
This issue is moved from https://bugzilla.mozilla.org/show_bug.cgi?id=1894447 Profile : https://share.firefox.dev/3JNDR49 Try going to the Marker Chart tab, or switch between different threads, or select a portion of the timeline and select...
Currently we have two types of track context menus. 1. Main track context menu on the top left corner for seeing all the tracks. 1. Process specific track context menus,...
Currently it's not possible to hide a type of tracks from the timeline and make it persistent across the profiles. On the Culture of Performance meetings, we got this feedback...
We should simplify the chart panel toolbar by: * Converting javascript/native checkbox to a selecbox. * Limiting "invert call stack" checkbox to call tree only.  ┆Issue is synchronized with...
Hi, I was looking at the developer documentation and found some deprecated APIs. For example, see the [`Workspace.activeLeaf` property](https://docs.obsidian.md/Reference/TypeScript+API/Workspace/activeLeaf). It has a warning like this: ``` Warning: This API is...