I’d like to carry this discussion here, as a feature request:
When the dark mode is toggled, there is no easy way to also toggle the logo.
Bricks’ Logo element natively supports inverse versions (used for sticky headers etc). Once this inverse asset is set, we should be able to also reference it via the dark mode toggle.
like mentioned in the other topic, I don’t have any news to share. But I bumped up this discussion internally, and I’ll get back to you once we have a decision.
It would be great if two new interactions were added for this feature. Beyond solving the challenge at hand, this would allow us to implement a wide range of scenarios—for instance, having a pop-up appear when dark mode is activated.
Hey @jolia, care to explain more? I don’t understand how new interactions are connected to the “Logo Inverse” feature.
If you think the new interactions would be needed, please open new Feature Requests / Improvements, and explain how they should work. Then I can take a look at them
What I have in mind is two new interaction triggers: Switch to dark mode and Switch to light mode. This enables the execution of various scenarios, including the subject of this report.
This enables the execution of various scenarios, including the subject of this report. For example, we apply an interaction to the light and dark logos so that if a “switch to dark mode” occurs, the light logo is hidden—and vice versa.
Or, for example, when dark mode is activated, a pop-up with the message “Dark mode activated” should appear.
As a professional programmer, does the implementation of this idea make sense to you? If so, I’ll submit a feature request.
I think it’s best if you open a new forum topic for this. This would require two new general interactions (or one, but with an option to select a condition). While the current task is about the Light/Dark mode logo inverse, it’s not connected to this, so it’s best if you open a new one.
We’ve addressed this in Bricks 2.4-beta (beta release), now available for manual download from your Bricks account.
Please read the changelog entry before testing, and let us know if you experience any issues. Note: beta builds are not recommended for production sites.