-
Notifications
You must be signed in to change notification settings - Fork 302
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
Fix toneMapping reference #455
Conversation
AFAICT, the spec requires toneMapping period. Even if the browser doesn't support toneMapping.mode = 'extended' it requires it still requires it to exist. It will just be set to `'standard'` if the implementation does not support `'extended'`. The only other case is when the canvas has not been configured in which case `getConfiguration` returns undefined. Both `getConfiguration` and `toneMapping` were added to the spec close enough that any implemetation that supports `getConfiguration` should be requried to include `toneMapping`.
You're right. See #451 (comment) |
@kainino0x I believe we can merge this PR. What do you think? |
I'd like to merge it. |
Sorry I forgot about this PR because I replied to the spec issue and PR instead. |
Can we just require
|
Require |
FYI Chrome always returns |
AFAICT, the spec requires toneMapping period. Even if the browser doesn't support toneMapping.mode = 'extended' it requires it still requires it to exist. It will just be set to
'standard'
if the implementation does not support'extended'
.The only other case is when the canvas has not been configured in which case
getConfiguration
returns undefined.Both
getConfiguration
andtoneMapping
were added to the spec close enough that any implemetation that supportsgetConfiguration
should be requried to includetoneMapping
.