Documentation: Remove exception for fog and background color #24929
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
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.
Related:
Description
The Color Management guide previously called out fog, background color, and clear color as exceptions to the general rule that three.js APIs accepting
THREE.Colorinstances assume RGB components in Linear-sRGB color space. For these properties, the choice had depended onrenderer.outputEncodingand whether or not post-processing was used. The exception has been resolved with #23937, and these colors are no longer a special case whenColorManagement.legacyMode = falseis configured (non-default in three.js, default in R3F).