Favicon change for Beta and Test environments

[petern]

To help quickly identify if you are in the production, beta or test environments, it would be useful if each had their own distinctive favicon.

We're currently doing this with javascript, but it's been really helpful so I thought others might benefit. Our icons are different colours and I have found that I rely on them a lot.

Main canvas site	https://xxxxx.instructure.com/
Test canvas site	https://xxxxx.test.instructure.com/
Beta canvas site	https://xxxxx.beta.instructure.com/

If an institution has a custom favicon in their theme then it could still be replaced in the test and beta instances.  

[KathyPalm]

Great idea to help add some additional visual clarity!

[MrAdam]

Good idea and ties somehow into my idea. 😀

[robotcars]

This is a great idea.

As someone who spends a lot of time in all three environments, I'll just share that I keep a different browser for Test and Beta. I typically use FireFox Developer Edition, and Chrome Canary, both are pre-release browsers for testing new features. Keeping Canvas Beta/Test in separate browsers means I don't accidentally have different environments open in the same browser, or click the wrong browser for a task as they each have a different icon. Obviously, if you're testing or developing custom JS&CSS with Themes, LTI's, UI, a final QA in production browser versions is necessary.

https://www.mozilla.org/en-US/firefox/developer/

https://www.google.com/chrome/canary/

[KristinL]

Thank you for sharing this idea with the Instructure Community!

The Product Team reviewed all feature proposals recently, and unfortunately, this thread was identified as one that they would not be able to include in their current or future plans. While we appreciate your proposal, we also want to be transparent about the likelihood of something like this making it to production.

Thank you for collaborating, and we hope that you submit another idea in the future!