Style generation, class list generation, etc needs testing

v2.3 should work as is, but there are at least a couple of transitions which would be missing: zoom and glow
https://semantic-ui.com/introduction/new.html

Tested with nightly 55.0.3
Needs investigating

Hi, I just noticed that the bounds on reflex and reflex-dom-core will need to be bumped to support the most recent obelisk versions. As I'm in the dark about release schedules on those and other OS upstream libraries, when would be a good time to do that?

A lot of the semantic-reflex widgets don't need the Prerender constraint, but they use the UI type alias so they get it. The result is that the user can't use these widgets in many places completely unnecessarily.

This also entails better export lists and probably adding Internal modules.

They are currently out of date and not compiling

I'm seeing build failures during the haddock phase. Heres' the error message:

haddock: internal error: internal: extractDecl
CallStack (from HasCallStack):
  error, called at utils/haddock/haddock-api/src/Haddock/Interface/Create.hs:1097:12 in main:Haddock.Interface.Create

Not very helpful I know, but that's all I've got for now. It seems to be crashing haddock in a way that doesn't display helpful error locations. :(

Moved from: obsidiansystems/rhyolite#90 (comment)

I'm seeing consistent test failure but only on Mac. Are there ways we can make the tests more reliable?

When a select element is focused, an option can be selected by typing in the text of the desired element. I've seen two behaviours: single letter search, where only the last entry is counted; and full entry search, where the entire entry is used and the user can even to make corrections.

This should share functionality with the true search enabled dropdowns, which have the latter behaviour but in a real text box, and the items are filtered.

Instead of _buttonColor we should probably have _button_color. Upstream would dictate _buttonConfig_color but I think that's too verbose.

This should be an optional feature that is enabled by default

Hey! I've been toying with doing a deeper dive to integrate Semantic-UI with reflex. Right now I'm using https://github.com/reflex-frp/reflex-dom-semui and it appears this is based on that somehow? I'm curious how these projects compare as I'd like to contribute.

I'd like to be able to change the default theme.
However, alot of the semantic-ui docs https://semantic-ui.com/usage/theming.html don't seem to make sense when I look at this repo.
For example, where is the site.variables file?

Currently the dropdown menu of searchDropdown is opened when the field is focused. It should only be open when there are items in the dropdown menu: if there are none it should stay closed, preventing the triggering of an opening animation.

I think the cabal version should be incremented when there is an API change, so I can specify a min_version in my app's cabal file. What do you think?

This functionality has been factored out into a separate function: dismissableMessage. I forgot to remove the old record field.

Should be replaced by UI in most cases

Pressing Up or Down arrow keys should skip over filtered items, but currently does not.

Could you document which version(s) of semantic UI (CSS) your library supports?