-
-
Notifications
You must be signed in to change notification settings - Fork 43
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LoAF origin trial #752
LoAF origin trial #752
Conversation
No issues adding but what’s the use case for enabling for everyone given we’re not sending LoAF data to analytics? Or is that planned for a future PR? I guess at least it enables it without having to enable all the other Experimental Web Platform features? |
Yeah I'd like to also include it in our analytics. I'd need more time to get familiar with it but I can follow that up in a future PR. |
I'm also supposed to be writing a blog post on LoAF. In which I should consider questions like this! :-) |
Looking forward to it! At least in our case, since we already have real-user INP issues, it'd be really interesting to see how that maps back to the real-user LoAF diagnostics. Setting the flag locally is probably good enough for most curious people. |
Not sure if it's too bleeding edge for web-vitals.js, but I filed a FR to add LoAF support to the attribution build: GoogleChrome/web-vitals#363 |
Working on this actually helped uncover a gap in the API: https://bugs.chromium.org/p/chromium/issues/detail?id=1473663 🙌 |
According to Search Console, we have an INP problem on our report pages. I think this is a good opportunity to try out the new LoAF origin trial in Chrome
115116 to see if it helps us narrow the problem down. While it might not be necessary for debugging, it's a good opportunity for us to dogfood the API.I've registered all HA subdomains for the trial and this PR adds the meta token.