Nazım Can Altınova
Nazım Can Altınova
After the changes in #56018 this test started to rely on `pagereveal` since the way we load the popup has changed. `pagereveal` is a new event type that's not implemented...
The test changes in #56018 are causing permanent timeouts in Firefox Nightly because Firefox recently changed its behavior to load `about:blank` synchronously. It aligns with other browsers, but this change...
Fixes #5715. This PR does three things: 1. Puts the category properly to the marker categories. 2. Removes the dummy payload if the event doesn't have any data. 3. Removes...
I noticed this issue when I was reviewing this PR: https://github.com/firefox-devtools/profiler/pull/5714#discussion_r2614080627 It looks like the way we currently add marker payloads are flawed. First we look at the chrome even...
I noticed that when we select something in the UI, and then dragging it. It's a very edge case, and it also thinks that I'm dragging and dropping a new...
Fixes #5640. This is not the ideal solution I had in mind initially. I initially wanted to add a new error, that shows this only when it's a JS file....
While I was looking at a profile I encountered this error when I pressed the back button: ``` TypeError: can't access property "color", n[s] is undefined. ``` And devtools console...
This has been in my mind for some time. Whenever I want to profile something, the first thing I do is to switch to the flame graph from call tree...
We have files like `bin/l10n-sync.js` that have JSDocs in them, but apparently we are not checking them with `yarn ts` correctly. See my comment here: https://github.com/firefox-devtools/profiler/pull/5659#issuecomment-3498430787 It would be good...
[Deploy preview] Try fetching every js source during the profile load and have a sanitization option
This is only a deploy preview, and **not** a PR that I intend to land. I only wanted to get a sense of profile size bloat if I were to...