edkv

In case this helps somebody, I've successfully built elm-format on Void Linux: ``` xbps-install ghc cabal-install ncurses-devel libnuma cabal update git clone https://github.com/avh4/elm-format.git cd elm-format ./build.sh -- build ```

I've tried the approach with storing hover state in the `Model` and now I think it's actually not that bad. The problem is that it will probably introduce many stateful...

>The main reason is that my goal is for Html.Styled to become ultimately unnecessary, if we get a way to do "virtual CSS" that does insertRule behind the scenes. At...

I'm against this - I think this solution would complicate the API a lot. How many problematic values do we have? `flex`, `left`, `right`, `top`, `bottom`, `content`, `text`, `color` -...

> Doing import Html.Attributes as Attr is basically the same thing. > > Do you think that's been a big burden in elm/html? @rtfeldman Actually, *maybe* it would be great...

If we didn't have issues with name collisions or had a way to use same names both for properties and values, would we still need to introduce a `Css.Property` module?...

@rtfeldman I want to implement `width`, `height`, `minWidth`,`minHeight`, `maxWidth` and `maxHeight`. I see they can also accept a few experimental values: `min-content`, `max-content`, `available`, `fit-content` and `fill-available` (also `fill` and...

I'll also take `boxSizing`.

At least the following properties are also experimental and should probably be removed from the list: ``` marginBlockEnd marginBlockStart marginInlineEnd marginInlineStart ```

Workaround: add `Element.htmlAttribute (Html.Attributes.style "flex" "1")` to the input.