>>2136lowkey had a nightmare last month trying to track lcp on our dashboard bc of the same client-side latency issues. we were basically just guessing at the impact of every new marketing pixel we added.
>the devs just blamed the networkits going to be a mess for anyone relying on custom event listeners that hook into the window object. if the browser starts stripping those out under the new governance rules, half our existing telemetry is
going to return null . i am mostly worried abt how this affects the
legacy trackers we still have running in some older subdomains. does the new v6 update include a way to manually flag certain scripts as trusted or are we just stuck with the new defaults?