Backoffice custom theme reset after reload / missing default theme option

[martin-prinz-mw]

Which Umbraco version are you using?

15

Bug summary

I've added a simple custom theme to Umbraco Backoffice.

It works fine, shows up in the Theme selection in the profile and selecting it also changes appearance as planned. However, I need these slight theming adaptions as a default. As I understood and observed, the selected theme is persisted in localStorage so the user preference survives page reloads. This works fine for the built-in themes, but not for custom ones added.

1. Do I miss something here, or might this be not yet working as intended?

2. Also, if there is an option to either extend the default Light theme or mark a custom theme as a new default, this would be very handy to fulfill our customer's requirements.

Specifics

No response

Steps to reproduce

• created an extension in App_Plugins with an umbraco-package.json
  umbraco-package.json

  // ...
  "extensions": [
    {
      "type": "theme",
      "alias": "my-theme",
      "name": "My Theme",
      "css": "/css/my-theme.css"
    }
]

• my-theme.css is placed in wwwroot/css/
• visit backoffice and switch to "My Theme" in user menu.
• refresh page
• observe umb-theme-alias: my-theme entry in localStorage being deleted after latest second page refresh
• observe "Light" theme being applied by default, as localStorage entry is gone

Expected result / actual result

• Expected umb-theme-alias: my-theme entry in localStorage to be persisted reliably

[github-actions]

Hi there @martin-prinz-mw!

Firstly, a big thank you for raising this issue. Every piece of feedback we receive helps us to make Umbraco better.

We really appreciate your patience while we wait for our team to have a look at this but we wanted to let you know that we see this and share with you the plan for what comes next.

• We'll assess whether this issue relates to something that has already been fixed in a later version of the release that it has been raised for.
• If it's a bug, is it related to a release that we are actively supporting or is it related to a release that's in the end-of-life or security-only phase?
• We'll replicate the issue to ensure that the problem is as described.
• We'll decide whether the behavior is an issue or if the behavior is intended.

We wish we could work with everyone directly and assess your issue immediately but we're in the fortunate position of having lots of contributions to work with and only a few humans who are able to do it. We are making progress though and in the meantime, we will keep you in the loop and let you know when we have any questions.

Thanks, from your friendly Umbraco GitHub bot 🤖 🙂