I would like to bring to your attention some concerns that we have regarding the integration of DevTools with the FLEDGE API. While we have previously filed issues #387, #389 on Github requesting improvements in this area, we have noticed some regressions that are making it difficult for us to debug and discover issues. Specifically,

1. We have observed that FLEDGE-related network requests such as requests to fetch seller and buyer scripts, trusted server calls, and Fenced Frame reporting pings are disappearing from both the network and performance tabs in DevTools. This is a major setback as we heavily rely on DevTools to debug and measure request latency and payload. Additionally, we also have automated profiling tools that rely on these features to work. We request that these network calls be restored to the network/performance tab. chrome://net-log is feasible but adds significant friction to the debugging flow.

2. We also ask that those network requests be exposed in the ResourceTiming API .This would allow us to measure and attribute latency to individual network callouts at scale, greatly improving our ability to identify bottlenecks and enhance performance.

3. Furthermore, we have noticed that console.log from seller and buyer scripts is missing from the selenium webdriver logs. This is a crucial feature that we previously had access to when debugging regression tests , and we would greatly appreciate it if it could be restored.

4. Cmd+shift+r hard refresh should also force cache renewal for decision/bidding logic script.