Does anyone have experience doing an off-ramp from elm-ui? Our applications have been built with it and usually have ~5 main pages each. elm-ui has been great, and truly is an accelerator in UI development, but we’re running into a few limits that are just awkward enough that I’m considering switching to good ol’ CSS. (If you’re curious: some documented scrolling bugs in modern Chrome, sticky headers on tables that scroll horizontally and vertically, some enter and exit animations I’d like to try out, and opinionated input not fitting our needs.)
Our apps follow the typical Page.A, Page.B with nested TEA. I see two basic options: top-down, converting the parent elements first with elm-ui children, or bottom-up doing the opposite. I’ve already noticed odd behavior on the few embedded Html we have.