Add deprecation on FID #2064
Open
Add deprecation on FID #2064
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
It has been deprecated and removed already by Google, and we want to align with the new standards.
ankur22
requested review from
inancgumus and
codebien
and removed request for
a team
inancgumus
approved these changes
Sep 19, 2025
| | --------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | ||
| | browser_web_vital_cls | Measures the visual stability on a webpage by quantifying the amount of unexpected layout shift of visible page content. Refer to [Cumulative Layout Shift](https://web.dev/cls/) for more information. | | ||
| | browser_web_vital_fid | Measures the responsiveness of a web page by quantifying the delay between a user’s first interaction, such as clicking a button, and the browser’s response. Refer to [First Input Delay](https://web.dev/fid/) for more information. | | ||
| | ~~browser_web_vital_fid~~ | This is deprecated in favour of INP. ~~Measures the responsiveness of a web page by quantifying the delay between a user’s first interaction, such as clicking a button, and the browser’s response. Refer to [First Input Delay](https://web.dev/fid/) for more information.~~ | |
There was a problem hiding this comment.
Would it make sense to remove FID? Or do you think people might still want to search for it?
If we choose to keep it, I think I'd tweak the text a little bit.
There was a problem hiding this comment.
We want to eventually remove it. We need to leave this in until we have deprecated the measurement in k6. Once it is removed from k6, then I think we can remove it from the docs, otherwise there could be some confusion why k6 is measuring this, but no reference of it being in the docs.
How would you tweak the text?
There was a problem hiding this comment.
I added a link to the official web dev blog post that contains more details.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What?
It has been deprecated and removed already by Google, and we want to align with the new standards.
Result
Checklist
npm startcommand locally and verified that the changes look good.docs/sources/k6/nextfolder of the documentation.docs/sources/k6/v{most_recent_release}folder of the documentation.docs/sources/k6/nextfolder of the documentation.Related PR(s)/Issue(s)
grafana/k6#5179