# Dark mode issue in Developer Canary Program Instances?

**URL:** <https://community.developer.atlassian.com/t/dark-mode-issue-in-developer-canary-program-instances/74600>\
**Category:** Confluence Cloud\
**Tags:** dark-mode, design-tokens\
**Created:** [November 10, 2023, 10:37am UTC](https://community.developer.atlassian.com/t/dark-mode-issue-in-developer-canary-program-instances/74600 "2023-11-10T10:37:36Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ajay](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/ajay/32/53765_2.png) [@ajay](https://community.developer.atlassian.com/u/ajay)\
**Post date:** [November 10, 2023, 10:37am UTC](https://community.developer.atlassian.com/t/dark-mode-issue-in-developer-canary-program-instances/74600/1 "2023-11-10T10:37:36Z")

</div>

Some of our test instances are enrolled in the Developer Canary Program, where we’re encountering problems with the Dark mode theme. However, these issues aren’t present in our non-Canary cloud instances, where toggling between Dark and Normal modes for the App is functioning correctly. Has anyone else noticed similar issues?  
I have created a ecosystem ticket - [ECOHELP-30036](https://ecosystem.atlassian.net/servicedesk/customer/portal/34/ECOHELP-30036)

---

<div class="post-metadata">

**Author:** ![ajay](https://sea1.discourse-cdn.com/atlassiandeveloper/user_avatar/community.developer.atlassian.com/ajay/32/53765_2.png) [@ajay](https://community.developer.atlassian.com/u/ajay)\
**Post date:** [November 17, 2023, 4:12am UTC](https://community.developer.atlassian.com/t/dark-mode-issue-in-developer-canary-program-instances/74600/2 "2023-11-17T04:12:34Z")

</div>

The ticket has been updated with the below comment identified as the root cause.

> Before our change, the CSS was being loaded as JavaScript, but after the change it is being loaded as a CSS file. This broke the CORS policy (which is what I saw above) and caused the error. We’ve turned off the Feature Flag causing this issue and the engineering team will go back to the drawing board to fix this.
