Skip to content

feature: add .form-caret class for reusable select-style caret#42051

Open
claytonlin1110 wants to merge 1 commit intotwbs:mainfrom
claytonlin1110:feature/form-caret-class
Open

feature: add .form-caret class for reusable select-style caret#42051
claytonlin1110 wants to merge 1 commit intotwbs:mainfrom
claytonlin1110:feature/form-caret-class

Conversation

@claytonlin1110
Copy link

Summary

Implements issue #41754: the form-select caret is now available as a separate .form-caret class so it can be used with form-control for typeahead, datalist, or any input that needs the same caret without full form-select styling.

Usage

<input type="text" class="form-control form-caret" list="options" placeholder="Type to search...">
<datalist id="options">
  <option value="Option 1">
  <option value="Option 2">
</datalist>

Relation

Fixes #41754

@claytonlin1110 claytonlin1110 requested a review from a team as a code owner January 30, 2026 15:41
@claytonlin1110 claytonlin1110 changed the title feature: add .orm-caret class for reusable select-style caret feature: add .form-caret class for reusable select-style caret Jan 30, 2026
@claytonlin1110
Copy link
Author

@mdo would you please review this?

@julien-deramond julien-deramond moved this to To analyze in v5.4.0 Feb 4, 2026
@claytonlin1110
Copy link
Author

Can someone review this?
cc @julien-deramond

@julien-deramond
Copy link
Member

Right now, we’re focusing on v6-dev branch with mdo and have temporarily paused reviews/merges into main (v5) until we establish a proper process, or simply have time to review changes for v5.
Depending on what lands in v6, we may cherry-pick this directly into v6 without including it in v5. That will depend on whether there will be another v5 minor release, which is still undecided.
Additionally, we haven’t yet determined whether #41754 is a feature that should be added to Bootstrap.

@claytonlin1110
Copy link
Author

@julien-deramond When could it be ready? can i change destination branch from 'main ' to 'v6-dev'?

@julien-deramond
Copy link
Member

There is no need to change the target branch. We will review the PR as is and cherry-pick the commit to v6-dev if necessary, or handle any required internal adjustments during the review process.

@claytonlin1110
Copy link
Author

Is there anyway to merge this PR to some other branch rather than main?

@claytonlin1110
Copy link
Author

cc @julien-deramond @mdo

@mdo
Copy link
Member

mdo commented Feb 21, 2026

@claytonlin1110 I appreciate the energy and earnestness, but as mentioned, our priority has been on v6-dev. That means we're not reviewing many other PRs right now, but that also means a LOT is up in the air still on what features we want to include, how form components evolve, etc. Please hold tight and we'll see what we can do.

It'd be extra work on our end, but maybe we can dual-track things after all to iterate on v5 and v6 simultaneously. That slows down a lot more, but it's possible.

Give us just a bit more time and we'll swing back to this and all the other open PRs/issues that we can :).

@claytonlin1110
Copy link
Author

@mdo Any ETA for review?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

Status: To analyze

Development

Successfully merging this pull request may close these issues.

Have the form-select caret as a separate class

3 participants