Using CSS Custom Properties as Runtime Design Tokens for Light/Dark Themes
Learn how CSS custom properties let you change colors, spacing, and other design tokens at runtime—no stylesheet swap or page reload required.
Loading…
ReadMeFeed / Community knowledge
#custom-properties
Real questions. Useful conversations. Find the people who know your stack.
css3Skill‑Based Matchmaking in Photon Realtime Using Custom Room Properties
Use Photon Realtime’s lobby‑visible custom properties to perform skill‑based matchmaking without a separate lobby. Set <code>CustomRoomPropertiesForLobby</code> on room creation and filter with <code>ExpectedCustomRoomProperties</code> in <code>OpJoinRandomRoom</code>.
photonengineCSS Custom Properties: Scoped Theming Without Preprocessors
Use CSS custom properties for dynamic theming, inheritance, and fallbacks without a preprocessor build step.
Using Photon Realtime Custom Room Properties for Dynamic Matchmaking
Find out how to use Photon Realtime’s custom room properties for dynamic matchmaking—set criteria on room creation, query with JoinRandomRoom, and keep everything inside Photon’s fast server. Includes a Unity example, trade‑offs, and next steps.
Less Mixins, Guards, and Pattern Matching vs CSS Custom Properties
Less mixins with pattern matching and guards shine at compile-time structure, but runtime theming belongs to CSS custom properties. Here's how to split the work — and verify it.
lessUsing CSS Custom Properties for Theme Colors: Scoping, Fallbacks, and Pitfalls
Learn how to define, scope, and safely use CSS custom properties with fallback values, plus common mistakes to avoid.
Photon Realtime Custom Properties: Verifying State Consistency After External Backup Restoration
Photon Realtime stores room state in Custom Properties that exist only in memory and are lost when the last client leaves the room. To recover a session after an unexpected shutdown, developers must persist these properties externally and re‑apply them when a new room is created. The goal is to confirm that the re‑applied Custom Properties accurately reflect
Inconsistent computed values for @property when redeclared with different syntax in cascade layers
Goal: Understand how the CSS @property rule should behave when a later declaration re‑defines the same custom property with a different syntax value, particularly whether the property’s value must be reset to its initial value to avoid duplicated writes in animation worklets. Uncertainty: The current specification does not define the interaction between casc
CSS var() fallback not applied when a custom property holds an invalid value type
Goal I want a design-token setup where var(--token, fallback) reliably protects components, so that if a token is ever assigned a value of the wrong type (for example a length where a color is expected), the component still renders with its declared fallback color instead of losing the declaration entirely. Constraint and uncertainty My understanding is that