Unsupported Style Properties

[mdgriffith]

I'm trying to come see if there are any missing style properties that style-elements does not directly support that it should.

If you've been using style-elements and have found yourself using Style.prop for any reason, I would love it if you could leave a note describing the situation you were using it in.

Some properties aren't supported on purpose, like z-index, because the library's goal is to make them not needed. However, it's still really useful to see where people had to do an override!

[gampleman]

We used position: sticky to do "chapter headers" ala iOS scrolling lists.

[AionDev]

I use Style.prop "user-select" "none" -- for some things that need to use drag and drop.

Style.prop "overflow-y" "auto" -- in drop-downs for example - there needs to be a scroll bar only if the nr of elements is exceeding a certain height. overflow on x is also a thing used often

I also use - but not as often.. Style.prop "user-drag" "none"

[thorebear]

I use Style.prop "border-top-color", Style.prop "border-left-color", Style.prop "border-right-color", Style.prop "border-bottom-color".

[bengolds]

I ended up using:

    attribute "style" ("transform: scale(" ++ xScale ++ "," ++ yScale ++ ")")

for scaling parentheses based off of their content, a la KaTeX. I had to manually calculate the content size as well, for xScale. If you want me to explain the use case in more detail, lemme know!

[akoppela]

In my case I've used "z-index" to implement calendar. I used buttons because they are focusable.

Without "z-index" outline of button would be overlapped.

So if you want to be explicit about it maybe something like onTop or bringFront, etc... could be the option to go.