You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
acreskeyMoz opened this issue
Jan 23, 2025
· 1 comment
Labels
featureWork that is user facing, and typically should be planned through https://airtable.com/shrRydo6UXhebmarkersAnything to do with marker data structures, marker chart, or the marker table
It would be helpful if the Chrome importer mapped network requests to network tracks in the Firefox profiler.
For example, when loading the following Chrome Performance trace in the Chrome performance panel, we can see how Chrome scheduled and executed the network requests: Chrome-login.yahoo.com Trace-20250122T160410.json
The text was updated successfully, but these errors were encountered:
canova
added
feature
Work that is user facing, and typically should be planned through https://airtable.com/shrRydo6UXheb
markers
Anything to do with marker data structures, marker chart, or the marker table
labels
Feb 5, 2025
That was indeed something I wanted to do, but couldn't get around to it.
I already have some notes on this, so let me put them here:
The network markers in the Chrome data is similar to ours, they are essentially a bunch of individual markers for some certain events, and they merge them together and generate synthetic network markers out of them. But the number of markers and the data is different than what we have.
featureWork that is user facing, and typically should be planned through https://airtable.com/shrRydo6UXhebmarkersAnything to do with marker data structures, marker chart, or the marker table
It would be helpful if the Chrome importer mapped network requests to network tracks in the Firefox profiler.
For example, when loading the following Chrome Performance trace in the Chrome performance panel, we can see how Chrome scheduled and executed the network requests:
Chrome-login.yahoo.com Trace-20250122T160410.json
However when we import this into the Firefox profiler, the network requests appear to be dropped:
https://share.firefox.dev/4h9GpsK
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: