-
Notifications
You must be signed in to change notification settings - Fork 396
feat: [UIE-10181] - Add light/dark theme identifier in Cloud Manager for Pendo #13381
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
base: develop
Are you sure you want to change the base?
feat: [UIE-10181] - Add light/dark theme identifier in Cloud Manager for Pendo #13381
Conversation
Cloud Manager UI test results🎉 866 passing tests on test run #2 ↗︎
|
Thanks @davyd-akamai! We may/should be able to use these custom attributes, which are generally more reliable in cases like this. Since HTML attribute selectors are valid CSS selectors, Pendo should support targeting them using selectors such as Pendo also has related docs that seems to support this approach:
Thanks for sharing the PR with Susana for confirmation on the Pendo use case. |

Description 📝
Currently, there's no identifer for third-party tools like Pendo to detect whether the app is in
lightordarkmode. This PR adds a theme identifier so Pendo can apply appropriate styling. Third-party tools (like Pendo) should be able to use this as selector:body[data-theme="dark"]orbody[data-theme="light"]Important
We're using a custom
data-themeattribute instead of a CSS class because it's the proper way to store application state according to HTML5 standards. CSS classes are meant for styling, and this approach avoids conflicts with our existing CSS while giving Pendo a reliable selector to detect the current theme.Changes 🔄
Scope 🚢
Target release date 🗓️
N/A
Preview 📷
How to test 🧪
Verification steps
<body>elementdata-theme="light"ordata-theme="dark"is present (based on the current theme)document.querySelector('body[data-theme="dark"]')(when in dark mode, should return element Otherwisenull)Author Checklists
As an Author, to speed up the review process, I considered 🤔
👀 Doing a self review
❔ Our contribution guidelines
🤏 Splitting feature into small PRs
➕ Adding a changeset
🧪 Providing/improving test coverage
🔐 Removing all sensitive information from the code and PR description
🚩 Using a feature flag to protect the release
👣 Providing comprehensive reproduction steps
📑 Providing or updating our documentation
🕛 Scheduling a pair reviewing session
📱 Providing mobile support
♿ Providing accessibility support
As an Author, before moving this PR from Draft to Open, I confirmed ✅