Carson Sievert

Closes #2058

The docs state that `selectOnTab` defaults to `false`, when in fact, it defaults to `true`. https://github.com/selectize/selectize.js/blob/e3f2e0b4aa251375bc21b5fcd8ca7d374a921f08/docs/docs/usage.mdx#L86 https://github.com/selectize/selectize.js/blob/e3f2e0b4aa251375bc21b5fcd8ca7d374a921f08/src/defaults.js#L21 Note that the default was changed here https://github.com/selectize/selectize.js/issues/945, but as other users have...

Sidebar navigation

9

The underlying component-level API could be something like: ```r page_fillable( navset_sidebar( nav_panel("A", "a"), nav_panel("B", "b") ) ) ``` And implementation wise could look quite similar to `navset_pill_list()` except uses `layout_sidebar()`...

This PR is motivated by Quarto (which already takes a build-time dependency on bslib to copy over it's modified version of Bootstrap) wanting to leverage even more work that we're...

`navset_card_*()` variants silently drop `header`/`footer` arguments

2

`Header`/`Footer` should appear above/below the relevant `nav_panel()` content (just like they would in the `navset_tab()` case. ```r navset_card_tab( header = "Header", footer = "Footer", nav_panel("A", "a"), nav_panel("B", "b") ) ```

Add input_check_search()

1

Hello world example: ```r shinyApp( page_fluid(input_check_search("foo", state.name)), function(...) {} ) ``` ## TODO - [ ] Move `inst/component/check-search.js` to TypeScript (i.e., `srcts`) - [ ] Should `input_check_search()` work without Shiny?

Closes #746 Closes #744 ### TODO - [ ] Add unit tests for these cases in `316-bslib-popover`