Bug 1639584 Comment 15 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

This has now hit release and is affecting users in bug 1643242 and:

https://reddit.com/r/firefox/comments/gvmw0h/firefox_77_update_broke_my_color_management/
https://reddit.com/r/firefox/comments/gvnx6l/770_color_management_no_longer_works/ 
https://reddit.com/r/firefox/comments/gwnjnt/color_management_still_broken_in_7701/
https://www.dpreview.com/forums/post/64006246

Since bug 1631615 was based on a wrong assumption, I assume it should be backed out at least for release?  
What's more important: windy.com or professionals with wide gamut monitors using `gfx.color_management.mode;1`, or is there a way to fix windy.com, while not regressing existing users' setups?
This has now hit release and is affecting users in bug 1643242 and:

https://reddit.com/r/firefox/comments/gvmw0h/firefox_77_update_broke_my_color_management/
https://reddit.com/r/firefox/comments/gvnx6l/770_color_management_no_longer_works/ 
https://reddit.com/r/firefox/comments/gwnjnt/color_management_still_broken_in_7701/
https://www.dpreview.com/forums/post/64006246

Since bug 1631615 was based on a wrong assumption, I assume the backport should be reverted at least for release?  
What's more important: windy.com or professionals with wide gamut monitors using `gfx.color_management.mode;1`, or is there a way to fix windy.com, while not regressing existing users' setups?
This has now hit release and is affecting users in bug 1643242 and:

https://reddit.com/r/firefox/comments/gvmw0h/firefox_77_update_broke_my_color_management/
https://reddit.com/r/firefox/comments/gvnx6l/770_color_management_no_longer_works/ 
https://reddit.com/r/firefox/comments/gwnjnt/color_management_still_broken_in_7701/
https://www.dpreview.com/forums/post/64006246

Since bug 1631615 was based on a wrong assumption, I assume the backport should be reverted for beta or maybe even release?  
What's more important: windy.com or professionals with wide gamut monitors using `gfx.color_management.mode;1`, or is there a way to fix windy.com, while not regressing existing users' setups?
This has now hit release and is affecting users in bug 1643242 and:

https://reddit.com/r/firefox/comments/gvmw0h/firefox_77_update_broke_my_color_management/
https://reddit.com/r/firefox/comments/gvnx6l/770_color_management_no_longer_works/ 
https://reddit.com/r/firefox/comments/gwnjnt/color_management_still_broken_in_7701/
https://www.dpreview.com/forums/post/64006246

Since bug 1631615 was based on a wrong assumption, I assume the backport should be reverted for beta or maybe even release?  
What's more important: windy.com or professionals with wide gamut monitors using `gfx.color_management.mode;1`, or is there a way to fix windy.com, while not regressing existing users' setups?

edit: I assume windy.com was incidentally fixed by bug 1639574 reverting the default `gfx.color_management.mode` to `2`, so a revert of the bug 1631615 backport would only affect those that *explicitly* want full color management.

Back to Bug 1639584 Comment 15