# Create a style class that i can bind to with non-dialog properties?

**URL:** <https://forum.inductiveautomation.com/t/create-a-style-class-that-i-can-bind-to-with-non-dialog-properties/76603>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [July 19, 2023, 7:20pm UTC](https://forum.inductiveautomation.com/t/create-a-style-class-that-i-can-bind-to-with-non-dialog-properties/76603 "2023-07-19T19:20:23Z")\
**Posts on this page:** 1\
**Showing post:** 5

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [July 19, 2023, 8:03pm UTC](https://forum.inductiveautomation.com/t/create-a-style-class-that-i-can-bind-to-with-non-dialog-properties/76603/5 "2023-07-19T20:03:01Z")

</div>

> [@ian.sebryk](#):
>
> ###### it would be nice if they'd show up in the dropdown too, wouldn't it?

Would require embedding a full CSS parser in the Java side of the application. Not impossible, but not a high priority.

You could make a 'stub' style class (with no actual effects) so that it shows up in the selector, and then do all of the actual CSS authoring in the stylesheet. The big downside there is maintenance burden. I'm personally in favor of the idea of allowing arbitrary CSS editing inside a style class (with a one-way operation to convert the builder into a plain text input), but I also don't make any decisions re: Perspective 😄

---

_[View the full topic](https://forum.inductiveautomation.com/t/create-a-style-class-that-i-can-bind-to-with-non-dialog-properties/76603)._