feat: adds forceRenderAllFields admin prop to force all fields in edit view to render immediately
#10478
Conversation
This file contains 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
…t view to render immediately
…forceRenderAllFields
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?
Adds new
forceRenderAllFieldsadminprop tocollection&globalconfigs forV3.This new prop forces all fields in the
Editview to render immediately, regardless of scroll position. By default, this is set tofalseto improve performance, as fields are progressively rendered to balance load times. Enabling this option can make it easier to locate fields using browser search (e.g., CMD+F).Why?
Previously, fields were only rendered to a certain viewport pixel height for performance purposes. As a result, this disallowed using the browser search on all fields in the edit view if they were not completely loaded in i.e in the proper viewport.