Add top-level highlights before the detailed migration notes. Link
the main changes to their related guides and component docs so
readers can find the upgrade steps.
* Prose: space blockquote and details children, keep media aspect ratio
Reboot removes margins from blockquote children, so paragraphs in a quote touch. Details had the same problem. Images with width and height attributes became distorted after max-width shrank them. Block-level media that are direct children stretched across the flex column. Also remove a duplicate img max-width rule.
* fix(prose): honor font weights and preserve excluded content
Custom font weights did not reach prose headings or description terms.
Use the shared weight tokens. Keep child spacing outside not-prose
content so an excluded block retains its own layout.
* docs(prose): show the elements covered by prose styles
The example used one-paragraph quotes and utility-styled placeholders,
so it did not show the spacing and media fixes. Add a disclosure,
plain images, heading code, and excluded content to show those rules.
* docs(prose): give the mobile example more room
The bordered example narrowed the text on phones. Extend its top and
bottom borders to the viewport edges, remove the side borders, and
add vertical padding. Keep its content aligned with the page gutters.
* docs(prose): replace the retired themes image
Use the existing Bootstrap and Vite illustration to show how images
keep their aspect ratio in Prose.
* feat(grid): prototype flexbox gutters with native gap
Size numbered columns and offsets against a gap-aware track width so
mixed spans fit the row without column padding or negative margins.
Keep standalone column widths and responsive row-column overrides.
Document the gutter migration and add real-browser layout coverage for
mixed spans, offsets, wrapping, nesting, RTL, and custom column counts.
* docs: highlight responsive grid columns in examples
Match column classes anywhere in the class attribute so responsive-only
columns receive the same background, border, and spacing as other grid
examples. Include the override locally while BUI carries the shared fix.
* docs: consolidate grid example highlighting
Keep the grid example override in the existing docs stylesheet and
include responsive equal-width columns such as sm:col. Remove the extra
stylesheet and retain the same styling for reordered column classes.
* ci: update bundle limits for gap-based grid sizing
Set the four affected CSS limits from measured gzip sizes. Round
limits up to the next 0.25 kB, as the bundlewatch helper does.
* test(grid): account for scrollbars in responsive layouts
Linux browsers reserve space for the vertical scrollbar. Use the
measured row width for expected column widths and offsets.
* fix(grid): preserve padded column widths and explain gap migration
Grid-only builds could wrap padded columns without Reboot. Include
padding and borders in column widths, and check both grid entry
points. Update migration and layout docs for native gaps, nested
rows, column breaks, and the gutter variables used by widths.
* docs(grid): remove container padding from previews
Native grid gaps no longer cancel container padding. Remove the
container classes from grid previews so the columns fill each
example. Keep the classes in the code and StackBlitz examples.
* docs(grid): remove containers from example snippets
Keep the grid previews, code snippets, and StackBlitz markup the
same. Remove container classes from the example source and remove
the preview-only filter. Explain when to add a parent container.
* docs(grid): keep example alignment in docs styles
Remove the outer wrappers and text-center classes from grid
examples. Center the labels with the component example styles.
Keep the code focused on rows, columns, and gaps.
* docs(grid): restore nested snippet indentation
MDX removes two leading spaces from the template lines. Add that
level back in the source so columns and their content remain
indented in the rendered snippets.
Themed chip links and buttons showed the primary focus ring. Use
the chip theme for the ring and for its dismiss button. Keep the
global focus color when no theme applies.
Show themed interactive chips in the docs. Cover direct and
inherited themes, active chips, and dismiss buttons in both modes.
* fix(combobox): support native form values and events
Multiple selections now submit one field per value. Commas stay in the
value, and an empty multiple selection submits no entries. Reuse an
explicit hidden input without removing application-owned fields.
Keep a stable field for input and change listeners. Sync fields before
notifications, restore initial selections on reset, and follow disabled
state and form ownership. Document the update and disposal contracts.
Forward Menu lifecycle events after its transitions. Keep native search
editing keys and cover the sticky search padding with logical CSS.
* feat(combobox): combine editable selection and chip entry
Search and select values from one editable field. Multiple selections
render as removable chips, and explicit free entry supports tags. Keep
query text separate from committed values and preserve native form data.
Use the existing Menu for positioning and lifecycle. Keep focus in the
editor while suggestions are highlighted. Preserve chip nodes, caret
positions, reset behavior, and input-method text during reconciliation.
Retire the separate Chips plugin and chip-input control. Keep static
chip styles and button-triggered Combobox markup. Document the alpha 2
markup, token, method, and event migration.
* fix(combobox): match chip fields to the default input height
Multiple values should fit the same row height as a normal input.
Use shared input spacing and typography, with smaller contextual chips.
Let the field grow when its values wrap.
Replace the text dismiss glyph with the SVG from the chip documentation.
Keep the named removal button and existing chip interaction behavior.
* fix(combobox): separate chip icon size from its hit area
Render the dismiss icon at 12px inside a 24px removal button. Move chips
closer to the field's inline start while keeping normal text padding
for an empty editor. Use logical spacing so the inset follows RTL.
* fix(combobox): tighten chip dismiss spacing
Use negative inline margins to bring the dismiss button closer to the
label and chip edge. Keep its 24px hit area and 12px SVG artwork.
* fix(combobox): derive chip corners from the field radius
Use a nested chip radius based on the wrapping field's radius, border,
and inset. Clamp the result at zero so square fields keep square chips.
* fix(combobox): balance chip insets within the field
Match the field's inline padding to its vertical padding when chips
are present. Derive chip corners from that inset and pull the dismiss
button's end margin in another 2px without reducing its hit area.
* fix(combobox): soften chip corners within balanced fields
Use half the field radius for chips so equal input padding does not
leave their corners nearly square. Keep square fields square.
* fix(combobox): restore chip selection and keyboard behavior
Highlight chips with the filled active state when users navigate or
select them. Restore modifier clicks, anchored ranges, select-all, and
deletion of highlighted chips. Keep native query editing and RTL keys.
Keep chip highlights separate from committed values. Report UI selection
through select.bs.combobox and restore the chip selection methods on
Combobox. Bulk removal honors each cancellation and emits one value
change before recovering focus.
Document the restored interaction and alpha migration. Cover range
anchors, duplicate values, disabled chips, reset, and disposal.
* fix(combobox): select chips on every focus path
Tabbing to a chip's remove button or focusing a chip directly should
show its primary selected state. Apply that highlight without changing
committed values, and dismiss the suggestion popup.
Guard focus controlled by range navigation and modifier clicks so it
does not collapse or undo the user's chip selection.
* fix(combobox): suppress inner chip focus outlines
Keep the filled selected chip and the wrapping field's focus ring as
focus indicators. Suppress the nested outlines on chips and their
remove buttons during keyboard navigation.
* fix(combobox): guard form and editor edge cases
Selection callbacks can change or dispose the component before an outer
operation completes. Stop stale selection and focus work after those
callbacks, and keep pending popup sizing from changing disposed markup.
Handle native composition events through the shared event system. Keep
unfinished input out of blur commits, reconcile completed composition,
and preserve focus after the editor loses it. Let the IME handle its
keys in both Combobox and Menu.
Follow external reset forms without a backing field, omit disabled
single options, and clear references to removed or disabled suggestions.
Add regressions and clarify the synchronous form update requirement.
* docs(chips): move standalone chips to Components
Chips can stand alone or appear within a form component. Place their
docs in Components and describe that wider use. Keep the old Forms URL
as a redirect, and update navigation and cross-links.
* fix(chips): limit hover feedback to interactive chips
Static chips change color and show a pointer cursor on hover, even
when they have no action. Keep static chips neutral and apply hover
feedback to links, buttons, and Combobox chips. A dismiss button keeps
its own hover state without changing the whole chip.
Add interactive examples and correct the documented CSS layer. Allow
for the extra selectors in the unminified CSS bundle budget.
* docs(combobox): lead with editable examples
Show search and selection in the input from the first example. Use
inputs for the shared examples and group the button variants together.
Use the editable markup in the form and setup guidance too.
* docs(combobox): restore the overview feature list
Describe editable inputs and button toggles in the original overview.
Include chips, free entry, form submission, and selection events.
* docs(combobox): preserve example indentation
Match the form field examples by adding the source indentation that
MDX strips. Record the convention in the docs guidance.
* fix(combobox): focus search directly when opening
Clicking a searchable combobox moved focus to the trigger before
the opening animation moved it to search.
Focus search as soon as the menu opens. Keep the trigger in the
tab order and return focus to it on Escape.
* docs(combobox): style the Language example label
* ci(combobox): fix bundle budgets and spelling
Round the three JavaScript bundle limits up to the next quarter
kilobyte to account for the search focus changes. Reword the docs
indentation rule so it passes the spelling check.
* fix(combobox): preserve resets and expose selection state
A canceled second reset could discard a completed reset. Keep each
pending reset until its own callback runs. Give button-mode options
listbox roles, handle Escape on the toggle, and restore chip focus
rings. Keep long values inside the field and use shared state tokens.
* fix(combobox): fit chips to the shared control size
Compact controls were 30px tall, but their fixed-height chips made
the multiple-selection field 34px tall. Derive chip and dismiss-button
heights from the space left by the control padding and borders. Check
compact, default, and spacious controls in the browser.
* docs(combobox): redirect chip input readers to the merged component
The former chip input page now points to Combobox. Explain the
consolidation at the top of that page and link the migration steps
for existing chip inputs.
* chore(combobox): account for the current main bundle size
The rebased build includes the merged Range and hash-link fixes.
Raise the three affected limits to the next standard budget step.
* feat(js): open collapses and tabs from URL hash links
Visiting a page with a fragment left opted-in collapses and tabs
closed, so deep links could not reveal their content.
Add `data-bs-hash` on the target. On load and hashchange, scroll
the trigger, show the panel, then scroll the target into view.
Fixes#34299
* fix(hash): keep fragment scrolling current after page load
A late import missed the initial fragment. An earlier opening could
also scroll after the user chose another fragment. Handle loaded
pages and ignore stale scroll callbacks. Wait for component opening
without leaving shown-event listeners after canceled events.
* fix(range): refresh decorations and honor form resets
Let applications refresh bubble configuration and datalist ticks with
update() while preserving constructor option priority. Keep drag events
on the value-only update path.
Refresh decorations after native form reset and release reset handlers
and pending work on disposal. Use a decorative div for the bubble so
WebKit cannot reset its inner markup as an output control.
Align the fill, bubble, and ticks with the native thumb in RTL layouts.
* docs(range): note accessible tick preset considerations
Record clickable labels as an optional future direction for sparse
presets. Require real buttons, keyboard activation, visible focus, and
usable targets while keeping ordinary ticks decorative by default.
* chore(range): account for the added bundle size
The Range refresh and reset fixes exceed three JavaScript bundle limits
by small amounts. Raise only those limits to the next standard quarter
kilobyte using the repository's bundlewatch helper.
* fix(range): honor shared radius and shadow tokens
Custom pill radii did not reach the range track or thumb. The track
also read a shadow token with no default. Use the shared tokens and
state the required prefix step for Sass builds.
* ci: publish npm releases with trusted publishing
Publish GitHub releases through npm OIDC authentication. Check the
package version against the release tag and build the package before
publishing. Send prereleases to next and stable releases to latest.
* ci: require maintainer approval for npm releases
Stage release packages for npm approval with two-factor authentication.
Install npm 12.2.1 so the workflow supports staged publishing without
relying on the npm version bundled with Node.js.
* ci: use npm 11 for release builds
npm 12 rejects the version_short config passed by the v5 build scripts.
Use npm 11.21.1 to support those builds and staged publishing.
* Keep unpadded accordion contents inside rounded corners
* test(accordion): cover panel corner edge cases
Exercise the reported non-flush list, logical RTL corners, and custom
border sizes. Add open menus with default and body containers to catch
clipping regressions from the panel overflow rule.
---------
Co-authored-by: Mark Otto <markdotto@gmail.com>
Document the browser floor, dialog behavior, and CSS customization
changes since alpha 1 so existing adopters can review their overrides.
Keep the v5.4 modal size mapping and list the new dialog size separately.
- Keep all nav items visible when they fit without the More toggle.
- Count gaps only between visible items, including the toggle when needed.
- Cover exact-fit and toggle-width boundaries.
Fixes#43214
- Keep an open dialog unchanged when an internal trigger targets that same dialog.
- Preserve link default prevention and document explicit dismissal.
- Cover self-targeted buttons and links.
Fixes#43072
- Preserve title and content attributes as written, including decimal and empty strings.
- Cover rendered Popover content, option precedence, and the text/HTML security boundary.
Refs #43090. The v6 fix is complete; the v5 backport remains tracked in that issue.
- Register distinct component types on the same element and use explicit keys for overlay cleanup.
- Cover component coexistence, disposal, and Combobox/Menu reuse.
- Add alpha 2 migration notes and document component lookup and ownership.
Closes#42965
The token was declared in $switch-tokens but never read, so the thumb kept
--switch-indicator-bg when checked. Use it in the checked ::before rule,
keeping --theme-contrast first so themed switches are unchanged.
Fixes#43143
* Restore the close button dark variant
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Apply suggestion from @julien-deramond
* Docs: show the close button dark variant on a dark example
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* Apply suggestion from @julien-deramond
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The sheet docs promise support for any placement, which suggests that
start and end sheets stay against the side of the viewport.
Describe the mobile bottom-sheet use case and its centered position
on larger screens. Point readers to regular drawers for side panels.
* fix(dialog): compensate scrollbar offsets with JavaScript
Pages with classic scrollbars reserve a permanent blank gutter even
when they do not scroll. Removing that gutter alone makes the page
shift when a dialog opens.
Measure root and full-width fixed-element expansion when locking
scroll. Restore the original inline styles after the last owner
closes. Share this lock between Dialog and Drawer, including native
close and disposal paths.
* chore(bundlewatch): account for the shared scroll lock
The new Dialog and Drawer scroll lock increases three JavaScript
bundles beyond their size limits. Raise only those limits to the next
quarter-kilobyte boundary using the existing budget update script.
* docs: raise the v6 browser support floor
Set the browser targets for the rest of the v6 release line and document
which platform features they make safe to use. Remove the stale unreleased
versions query and clarify which newer features remain unavailable.
* docs: address browser support review feedback
Keep the minimum-version table in two columns on small screens.
Clarify that the higher browser floors expand support for features
already used as progressive enhancements in alpha 1.
* docs(alert): improve content examples
Explain the alert flex layout and show how to create simple and complex
content layouts with utilities and markup.
* docs(alert): stretch vertical content
Stretch the vertical alert content across the available width and use
valid JSX syntax for the horizontal rule.
Temporal input indicators stay next to their value when the input grows.
Position the native indicator against the input so it stays at the inline
end of the control.
The full non-bundle build uses bare module specifiers for Floating UI
and Vanilla Calendar Pro. Explain that browsers need an import map for
both dependencies, and use the bundle in the direct-loading example.
Pages with long closed dialogs retain their dimensions and gain extra
blank space because Bootstrap overrides the browser's hidden display.
Use display only while the dialog has its open attribute. Keep the
existing exit transition active until JavaScript removes that attribute,
and add starting styles to preserve entry transitions.
* New breadcrumb variable for divider spacing
This change adds a new breadcrum divider variable for cases when we need the breadcrumb to be flush with the content, but also control the spacing for the breadcrumb divider.
The old way was calculating the margin inline based on the divider item's padding-x and dividing it by a value (4), but if padding-x was set to 0, there was no way to customize this without applying an utility class over the divider element itself.
* Update scss/_breadcrumb.scss
Co-authored-by: Mark Otto <markdotto@gmail.com>
* Added alert component custom border width support
* Remove alert border width variable
This was supposed to be for a different PR.
* Update scss/_breadcrumb.scss
---------
Co-authored-by: Mark Otto <markdotto@gmail.com>
* chore(release): prepare Bootstrap 6 alpha
Update release guidance and version tooling for the first Bootstrap 6
alpha from main. Remove stale v6-dev workflow references, pin the
prerelease in agent skills, and make future version updates reliable.
* chore(dist): rebuild for v6.0.0-alpha.1
* docs: use the local logo in the README
Load the tracked Bootstrap logo instead of the deployed documentation
asset, and remove the obsolete fixed height.
* fix(docs): keep the README logo path spellcheckable
Use the literal version placeholder in the local logo path so cspell does
not parse the percent-encoded bracket as an unknown word.
* fix(docs): make site copy cross-platform
Running `npm run docs-build` on Windows fails after Astro finishes
because the build command relies on Unix `rm` and `cp` utilities.
Move the cleanup and recursive copy into a Node script so the docs build
uses the same filesystem operations on every supported platform.
* fix(docs): make Astro cleanup cross-platform
Running the Astro cleanup task on Windows fails because it invokes the
Unix-only `rm` command.
Remove generated Astro directories with the Node.js filesystem API so
the task works consistently across supported platforms.
The asynchronously loaded desktop ad shifts the centered masthead content
when it appears.
Wrap the ad in a stable container and reserve its minimum height at medium
viewports and above so the masthead keeps its initial position.
Docs type errors could accumulate unnoticed because the main lint task did
not run Astro's checker. Add it to the lint suite and correct the existing
component, route, and third-party integration types.
Example pages without a trailing slash resolved local CSS and JavaScript
against the examples root. Resolve relative assets from the canonical
example directory so both URL forms load the same files.
* refactor(docs): consume shared Astro UI primitives
Use the local docs UI package for head metadata, theme controls, search
markup, and Pagefind behavior while retaining Bootstrap-specific layouts,
content readers, versioning, examples, and build integration.
* refactor(docs): delegate the shared shell to docs UI
Replace local navigation, search, theme, layout, footer, ads, and
Table of Contents copies with thin adapters to @twbs/docs-ui.
Keep documentation-only scripts, sidebars, content readers, and examples
local while deduplicating Bootstrap's browser module and shared Sass.
* refactor(docs): consume shared code examples
Delegate Code, Example, ResizableExample, highlighting, clipboard
behavior, placeholder parsing, and example styles to @twbs/docs-ui.
Keep only thin Bootstrap configuration adapters for repository links and
config token replacement.
* refactor(docs): consume the published BUI package
Resolve the shared shell, examples, browser helpers, and styles from
@twbs/bui 0.1.0 instead of a sibling checkout. Configure Bootstrap's Sass
source for the package peer and keep the calendar peer available to docs
builds.
Use BUI's canonical footer configuration so project links stay aligned
across Bootstrap sites.
* fix(docs): refine mobile docs actions
Give page introductions more room below the mobile navbar and use compact
text for the table-of-contents control. Present install downloads as simple
accent links so they fit their table cells cleanly.
* fix(docs): update BUI for self-hosted installs
Bootstrap's root package cannot satisfy a required peer of its docs UI,
so clean installs tried to fetch the unpublished Bootstrap alpha.
Update to BUI 0.1.1, which keeps the compatibility range while making
Bootstrap optional for the self-hosted documentation build.
The range fill, thumb, and thumb hover ring read --primary-base
directly, so .theme-* had no effect on .form-range, unlike .check and
.switch. Fall back from --theme-bg / --theme-focus-ring to primary in
the range tokens, and document the theme colors.
The divider is a `::before` positioned with the physical `left`, so in RTL
it lands on the outer edge of the second button instead of between the two
buttons. Use `inset-inline-start` so it follows the writing direction.
Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
* feat(tables): add `.table-card` for rounded tables
People often nest tables in cards to get a bordered, rounded look.
That creates padding, margin, and double-border edge cases.
Add a `.table-card` wrapper that clips and rounds the table itself,
and document the utilities-only equivalent.
Closes#39774
* fix(tables): silence stylelint on `.table-card` cell selectors
The last-row border reset needs the same deep universal cell path as
`.table`, plus a wrapper and optional responsive nest. That trips the
compound, universal, and combinator limits.
* chore(css): increase table-card bundle limit
* fix(forms): always float labels on date and time inputs
Date, time, datetime-local, month, and week inputs do not support
placeholders like text fields, so floating labels looked filled even
when empty and padding stayed inconsistent.
Keep those controls (and selects) in the floated label and padding
state, and document the behavior.
Fixes#39257
* fix(forms): mute date/time separators and dedupe docs
Date and time inputs show hard `/` and `:` dividers that fight the
control’s muted placeholder look in WebKit and Blink.
Color those separators with the control placeholder token, and fold the
duplicate date and time docs section into one.
* feat(forms): add always-floating labels for v6
Port the always-visible floating label opt-in from #36155 to the v6
token and label-first :has() model.
Show placeholders on focus by default, and add .form-floating-always
to keep the label floated with a visible placeholder.
Supersedes #36155
* fix(forms): pass floating label CI checks
Use lint-compatible date, time, and select selectors while preserving
their matches. Raise the minified CSS budget to cover the new floating
label rules.
A range selection without addToSelection calls clearSelection(), which
also resets the anchor chip. The next Shift+Click then has no anchor and
falls back to a single selection. Keep the anchor across the reset.
* fix(popover): keep dismiss-on-next-click open inside the tip
Selecting text or focusing a control inside a focus-triggered
popover closed it, because focus left the trigger.
Keep the tip open for tip focus and tip pointerdown, and dismiss
on outside pointerdown instead.
Fixes#31088
* Bump bundlewatch limits for the tooltip tip-interaction logic
Raise the bootstrap.min.js and bootstrap.bundle.min.js size limits to fit
the added tooltip focus and pointer handling.
* bump
Update the migration guide and agent skills for current component markup,
theme classes, dependencies, container queries, and JavaScript behavior.
Remove stale Calendar guidance and document native Drawer markup, current
browser floors, and the bundled versus standalone dependency model.
Publishing the docs meant building the site and pushing it to gh-pages by
hand. This adds a workflow_dispatch job that builds the site, then copies it
over a gh-pages checkout with rsync. The copy omits --delete, so every older
docs/<version> directory survives while the root files and the current version
get replaced.
The job uses no third-party actions. GitHub's own Pages actions replace the
whole site on each deploy, so they cannot keep the version archive.
Also drop release-drafter. The release UI now generates the notes, and
.github/release.yml keeps the same label categories.
Give maintainers a project skill for the full release path. Include
version preparation, validation, package publishing, release assets,
NuGet publishing, documentation deployment, and final checks.
Require explicit approval before each external release write.
* fix(docs): omit SRI for local assets
The docs site serves its bundled assets from versioned local paths, but the
helpers attach hashes for CDN files in production.
Stop adding integrity attributes to these local URLs so browsers load built
assets when their content differs from CDN artifacts.
* fix(js): remove component listeners on dispose
Disposed chips, comboboxes, and strength meters leave listeners attached to
child elements because their events do not use component namespaces.
Namespace these listeners and remove them during disposal while preserving
listeners that consumers added.
* fix(datepicker): synchronize parsed values
Date-only input values can shift by one day outside UTC, and programmatic
selection changes do not update connected inputs and display elements.
Parse date-only values in local time and route all selection updates through
the same value synchronization path.
* fix(dialog): respect backdrop and swap cancellation
Dialogs and drawers with no backdrop still close on an outside click. Dialog
swaps also close the source when either lifecycle event cancels the swap.
Honor disabled backdrops and check both cancelable lifecycle events before a
swap changes either dialog. Register focus restoration only for accepted
shows.
* fix(tab): ignore stale activation completion
Rapid tab activation lets an earlier transition finish after a newer one. The
stale callback then restores the wrong selected and accessibility state.
Track each activation request and ignore callbacks that no longer match the
latest request.
* chore(bundlewatch): raise JavaScript size limits
The required component fixes increase three generated JavaScript bundles
beyond their existing gzip limits.
Raise each limit to the next quarter kilobyte with the repository's
Bundlewatch update tool.
* Add token playground to theme docs
Show how theme and layout tokens flow to components. Readers change the
radius, spacer, or primary color and see the button, input, alert, and
card update together. The Remint control demonstrates how derived tokens
(bg-subtle, fg, border) restate the theme today.
* Add remint to cspell word list
Clicking the navbar search button opens the dialog but leaves the search
field unfocused. Keyboard shortcuts already focus it.
Focus the field after the dialog entry transition so pointer focus cannot
return to the trigger.
* Add failing test when pasting into OTP input
* Fix OTP input pasting being truncated
* Reduce bundle size, test for disposing paste listener
* fix(otp-input): preserve native paste behavior
Pasting a formatted OTP avoids maxlength truncation, but the custom
handler replaces the complete value for every paste and changes readonly
fields.
Insert partial codes into the selected range, replace the existing value
only for complete codes, and leave readonly or empty pastes unchanged.
Update the paste tests to emulate native maxlength insertion.
* perf(otp-input): reduce paste handler bundle size
The paste behavior fix pushes the unminified bundle above its size limit.
Reuse mutable selection bounds instead of repeated conditional expressions
to preserve the behavior with less generated code.
---------
Co-authored-by: Sondre Aasemoen <sondre@eons.io>
* Close plain navbar drawers on resize past expand
The resize handler only matched responsive `.{bp}:drawer` classes, so
navbar drawers using plain `.drawer` stayed open after expand and kept
overlay styles. Widen the selector and cover it with a unit test.
* fix(drawer): track navbar container resizing
Change an open navbar's width without resizing the viewport: its drawer
can expand inline while the native dialog stays open.
Observe the containing navbar and close the drawer after its computed
position becomes static. Limit resize scans to valid drawer classes so
unrelated dialogs stay open.
* chore(bundlewatch): raise the bundle size limit
The drawer resize observer raises the compressed unminified bundle above
its current limit. Increase that limit by 0.25 kB to cover the change.
Unit tests use nested callbacks for Jasmine structure and async events.
Disable that rule for unit specs. Exclude local Cursor metadata from
Git and ESLint.
* Update placeholder sizing, docs, and animations
* feat(placeholders): favor shimmer for loading states
Use the wave animation for loading skeletons and inline status text.
Move the old opacity effect to placeholder-pulse while keeping the
placeholder-glow class as a compatibility alias.
Update the component docs, migration guidance, migration skill, and
docs search loader to use the new recommendation.
* Fix bundlewatch
* Relocate overflowing nav menus as overflow submenus
A nav item that hosts a menu used to collapse into a plain cloned link.
The menu became unreachable once the nav item overflowed, so a nested
menu was lost at narrow widths.
Move the original `.menu` into a `.submenu` of the overflow menu instead
of cloning it. One live menu keeps its ids, its nested submenus, and its
node state. Only the trigger is cloned, with the menu data attributes
stripped and `aria-haspopup` added. Restore moves the menu back to its
nav item and disposes the menu instances that were created.
* Type a relocated menu parent as ParentNode
`tsc` rejected `parent.append(menu)`, because `Node` does not declare
`append`. Store the parent as `ParentNode`, which does, and which is what
`Node.parentNode` already returns.
* Raise the JS bundlewatch budgets
The submenu relocation adds about 0.4KB gzipped to the minified builds,
and both budgets had under 0.1KB of headroom. Move
`bootstrap.min.js` to 34.0KB and `bootstrap.bundle.min.js` to 56.0KB.
* Handle menu state during nav overflow relocation
An open nav menu kept stale classes when its item moved into overflow.
Menus moved to another container were also missed, and cloned anchor
triggers lost keyboard focus.
Cache each hosted menu before it can move, reset open state during
relocation, and keep anchor triggers focusable. Add regression coverage
for relocation, nested interaction, container menus, and menu rebuilds.
Raise the bundled size budget to fit the added handling.
* Raise the unminified bundlewatch budget
The bundled build is 73.13KB after the nav overflow changes, which is
above the 73KB limit. Raise the limit to 73.25KB.
* Fully round nav pills
The radius token leaves visible corners on taller pill navigation. Use a
component-specific 3rem radius for the pill container and links.
* Fix nav overflow startup and clipped menus
Resizable examples clip the generated overflow menu because their fixed
positioning strategy cannot reach the toggle that NavOverflow creates.
Expose a menu strategy option and use it in those previews.
Hide the expanded nav until its first calculation completes to prevent a
startup flash and scrollbar. Remove the icon line box so icon-only toggles
stay vertically centered.
* Update Vanilla Calendar Pro to v3.4.0 and register only needed extensions
VCP v3.4.0 moves its optional features into extensions that ESM users must
import. The datepicker now registers only `months`, which
`displayMonthsCount` needs. This keeps time, weeks, motion, and annotations
out of `bootstrap.bundle.js`.
The v3.4.0 core is still larger than v3.2.0, so `bootstrap.bundle.min.js`
grows from 55.98 kB to 57.32 kB gzipped. Raise its budget to 57.5 kB, and
lower the unminified bundle budget to 73 kB.
Add `Datepicker.registerExtensions()` so that pages can enable other
features for every datepicker, including those the data API creates.
Extensions in `vcpOptions.extensions` merge with the registered set. The
docs show only core features, plus an Extensions section that explains how
to add the others.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01BSipmEzpamwBN3vxKsUcge
* Revert "Add a calendar docs page"
The calendar docs page came with the calendar and datepicker split,
which landed on v6-dev by accident. We are not keeping the split, so
remove the page and its sidebar entry.
This reverts commit 04e526914.
* Merge the calendar Sass back into the datepicker
The calendar and datepicker split landed on v6-dev by accident, pushed
straight from a local branch instead of through this PR. We are not
keeping it, so restore the single `_datepicker.scss` and its
`--datepicker-*` tokens, and drop the calendar tokens from the docs and
the migration guide.
Keep the fix for the month and year grids. VCP 3.2.0 and later wrap
months and years in row and cell elements, so the column grid still has
to go on the row.
The split also broke popup dismissal. The popup rule set `opacity: 1`
with more specificity than `[data-vc-calendar-hidden]`, so a hidden popup
stayed visible. The single file keeps the two rules at equal
specificity, and the hidden rule wins by order.
* Fix the theme sync by caching the ancestor on first lookup
* Let vcpOptions.type through and style VCP's animated transitions
These changes come from the VCP 3.3.1 bump, which a force push dropped
from this branch. The version bump itself is no longer needed.
The datepicker always set VCP's `type` itself, so `vcpOptions.type` was
silently ignored. Let it through when `displayMonthsCount` is 1. More
months still force VCP's required `'multiple'` type. In v3.4.0 the
`'week'` type needs the `weeks` extension, so document that.
With animation on, VCP clips the outgoing view and layers a ghost clone
on top of it. Without the clip and the absolute positioning, the clone
stays in normal flow and shows through under the calendar. Style
`[data-vc-clip]`, `[data-vc-ghost]`, and `[data-vc-collapsing]`.
Co-authored-by: Mark Otto <markdotto@gmail.com>
* Point the VCP CDN URL at v3.4.0
The v3.4.0 upgrade bumped the package but left the docs CDN URL on
v3.2.0.
* Drop the week view and the weeks extension
We do not want the week view, week numbers, or collapse to a week, so
stop supporting them. The datepicker sets VCP's `type` itself again, and
`vcpOptions.type` no longer reaches VCP. Remove the `[data-vc-collapsing]`
styles, the `weeks` row in the extensions table, and the `weeks` usage in
the docs, unit tests, and type tests. The tests use `motion` and `time`
as the sample extensions instead.
* Support only the months extension and drop registerExtensions()
We do not style or test VCP's optional features, so stop offering them.
The datepicker always passes `extensions: [months]`, which
`displayMonthsCount` needs, and ignores `vcpOptions.extensions`. Remove
`Datepicker.registerExtensions()`, the animated transition styles for
the `motion` extension, and the extensions docs. The docs now say that
options from other extensions are not supported.
* Close the datepicker on outside presses and on a second trigger click
VCP hides the popup on an outside click itself, but it skips Bootstrap's
hide events. Close it on `pointerdown` outside the trigger and calendar
too, so presses on non-focusable elements fire `hide.bs.datepicker` and
`hidden.bs.datepicker`. The same handler already covers `focusin`.
VCP also schedules a show on every click of its trigger, after the data
API toggle runs. A second click on a button trigger closed the popup and
VCP opened it again. Cancel that reopen when the toggle closed it.
The two fixes add about 90 bytes, so raise the `bootstrap.min.js` budget
to 33.75 kB.
* Typo
---------
Co-authored-by: Claude <noreply@anthropic.com>
Co-authored-by: Julien Déramond <juderamond@gmail.com>
.form-select was consolidated into .form-control on <select> elements,
but these two selectors in the input group border-radius rules still
targeted the old class. They no longer matched anything.
Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
React Bootstrap has no Bootstrap v6-compatible release yet, and its
components render their own DOM, so pairing it with v6's CSS breaks
styling entirely. The example was dropped from twbs/examples' v6-dev
branch for the same reason (twbs/examples#997); this removes its
listing from the docs examples page to match.
Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
$root-tokens hardcoded --spacer: 1rem instead of interpolating
$spacer. Every --spacer-N token derives from $spacer through the
$spacers map, so overriding $spacer moved the scale but left the
base token stuck at 1rem. Other tokens in the same map already
interpolate their Sass variable (e.g. --border-width), so this
brings --spacer in line with that convention.
Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
--nav-tabs-link-active-color and --nav-underline-link-active-color
referenced --fg-color, a token that does not exist. Use --fg-body,
the same token .nav-link-active-color already uses for this state.
Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
--btn-font-weight referenced var(--btn-input-font-weight), but that
token was never declared alongside its --btn-input-* siblings. Add it
to scss/_root.scss so buttons resolve the intended font weight
instead of silently inheriting.
Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>
A fast double-click on a swap trigger opened both dialogs with a doubled
backdrop. The second click hit the just-opened dialog's own swap trigger
before its entry transition ended, so the outgoing dialog could not hide.
Ignore a swap trigger while the outgoing dialog still has .dialog-swap-in.
Reported at https://github.com/twbs/bootstrap/discussions/42444#discussioncomment-18384037
Co-authored-by: Claude <noreply@anthropic.com>
The alert tokens held the `--theme-*` lookups themselves, so anyone who
overrode `--alert-bg` or `--alert-color` also lost the theme fallback. Move
each lookup to the declaration that uses it. The tokens now hold plain base
values, and a `.theme-*` class still wins.
Compose the border in the declaration too, and drop the `--alert-border`
token that only wrapped the other three.
Round the corners with `--radius-7` to match the other surface components.
CSS Color 5 requires a <percentage> for the color-mix() mixing weight. A
bare number parses in a custom property declaration, but makes the value
invalid at computed-value time. Every .navbar-dark link color was dropped,
and the element inherited its color instead. No browser reports a warning.
The four values came from the v5 rgba($white, .55) form and kept the
decimal. The other 28 color-mix() calls in the stylesheet use percentages.
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Document all spacing values through step 12 across margin, padding,
gap, space, gutters, and utility API examples. Correct the responsive
space syntax and custom negative-map example.
Expand border-radius examples through step 9 and show the correct Sass
map and generated root tokens.
Reduce the introductory text size on narrow screens, increase the
action gap, and use keyline menu dividers. Remove the redundant
masthead button shadow override.
Send the Examples navigation item to the dedicated v6 examples
repository. Store the URL in shared config and mark the link as
external in both navigation layouts.
Add quarter-step spacing values through 3rem and smooth the largest
radius steps. Update the migration guide and migration skill with the
new utility mappings.
Put the outer border on the card and use single dividers between its
content sections. Remove the temporary card-list helper and let flush
list groups inherit the card corners.
Update body alignment, grouped cards, examples, and migration guidance
to match the new structure.
The last two weeks added :host tokens, defaults() map
merges, accordion modifiers, hoverable tooltips, and a
standalone calendar. The migration guide omitted them,
and the agent skills still described the old APIs.
The calendar now has its own Sass partial and token map, so document it
apart from the datepicker. The page covers the inline calendar, the
`--calendar-*` tokens, and the color modes.
Point at the datepicker for options, methods, and events, because the
calendar has no JavaScript of its own.
VCP 3.2.0 wraps the months and years in row and cell elements to fix
their ARIA grid structure. That change moves the grid columns off the
container, so put the column grid on the new row elements. The month and
year views otherwise collapse to three rows.
Also split the calendar grid out of the datepicker into its own Sass
partial and token map. The datepicker now layers the popup surface onto a
bare calendar, instead of inline calendars undoing the popup styling. Use
the `--calendar-*` tokens to style a calendar and the `--datepicker-*`
tokens to style the popup.
Add unit tests that pin the month and year markup, because this
regression was invisible to the suite.
Closes#42836
Spacing accordion items apart used to need a custom margin on each item.
A margin joins the panel block-size transition, so adjacent items jumped
while a panel opened.
Add `.accordion-gap`, which lays the accordion out as a flex column and
puts the space in `gap`. A flex gap stays constant during the transition.
Each item clips its overflow and keeps a full border radius, so corners
do not retarget while the panel opens. Set the space with the new
`--accordion-gap` token.
Mix colors in oklch instead of lab, so a tint or a shade keeps a more
even lightness across the palette. Pull the 950 and 975 shades back to
70% and 76%, because the darkest steps had collapsed together.
Mix the dark mode `--border-subtle` from gray-800 and gray-900. Plain
gray-900 was too close to the dark body background to read as a border.
Let an active nav pill follow `--theme-bg` and `--theme-contrast`, so a
theme utility on a pill nav now takes effect.
Fix the swatch shortcode, which split `light-dark()` on the first comma.
A nested `color-mix()` broke that split and fell back to the raw string.
Match parens instead, and unwrap `var(--token)` for display.
Document the border tokens that already shipped: `bg`, `body`, `white`,
and `black`.
Open a dialog with `show()` and it sits off center. `show()` does not use
the top layer, so the dialog needs its own positioning. That positioning
centered the dialog with `translate(-50%, -50%)`, but the open state sets
`transform: none` to end the entry animation. The transform reset then
removed the centering.
Center with `inset: 0` and the `margin: auto` already on `.dialog`, and
add `height: fit-content` so the block axis also centers. Nothing here
depends on `transform` anymore.
A breadcrumb added a bottom margin of its own, so it fought the spacing
utility or the layout gap around it. Remove the
`--breadcrumb-margin-bottom` token and set `margin-bottom: 0` to clear
the browser default on the list. Spacing is now the page's job.
* Refresh the homepage masthead
Link the v6 announcement post, which is now live. Widen the headline
column to `lg:col-10` so the lead paragraph breaks over fewer lines.
Group the install command, the agents link, and the docs button on one
row from the `md` breakpoint, and wrap the docs button in an accent
shadow so it reads as the primary action.
Point the second footer link at the Bootstrap 5 docs. It used to repeat
the install page that the docs button already opens. Use the absolute
`getbootstrap.com` URL, as `Versions.astro` does, because the v5 docs are
not part of this build.
* Format the masthead with Prettier
`docs-prettier-check` runs as part of `npm run lint` and rejected the
new markup. Wrap the long anchors the way Prettier wants.
The fixed example theme picker leaves space for a chevron that its icon
set does not include. The menu also opens toward the viewport edge.
Use a square icon button in examples and open its menu above the button.
Keep the full theme picker in the documentation navigation.
* feat(css): add .theme-reset to drop inherited theme tokens
Put .theme-reset on a nested container inside a .theme-* subtree.
Theme-aware children then use their component fallbacks again.
.theme-* tokens inherit by design. There was no way to return to
unthemed defaults. This class sets each --theme-* custom property
to initial so var(--theme-*, fallback) uses the fallback.
* chore: bump bootstrap-utilities.css bundlewatch limit
.theme-reset ships with the theme helper classes. The utilities
CSS is 19.28 kB gzip, which is over the 19.25 kB cap.
Let users move the pointer onto the tip without it hiding, so they can
reach interactive content inside it (WCAG 1.4.13). Track the original
trigger for delegated tooltips and attach matching leave listeners on
the tip element. Add an "Interactive tooltips" docs example and note the
behavior in the accessibility section.
Closes#28411
Supersedes #35151
Co-authored-by: Ryan Berliner <ryan.berliner@gmail.com>
* Use `:host` in root selectors so Web Components can access CSS vars
Reproduce twbs/bootstrap#37162 on v6-dev. Adds `:host` beside every
`:root` selector that emits CSS custom properties, so components styled
in a shadow root see the tokens.
* Point the CSS variables snippet at `:root, :host`
Netlify compiles CSS before the docs site. The old `:root {`
regex no longer matches after we add `:host`.
* docs: wrap TOC titles and fade the scroll edges
Long heading names were clipping in the sidebar. Wrap them and
fade the list when it overflows so the current section stays
readable.
* Remove comments on fade effect for scrolling
Removed comments about fading edges for scrolling.
* Fix Sass theme map configuration and merge overrides via defaults()
bootstrap.scss never forwarded the theme module, so configuring
`$theme-colors` through the entrypoint with `@use ... with (...)` failed
with a "not declared with !default" error. Forward the theme module to
expose the theme maps for configuration.
Also convert the theme maps to the defaults() pattern so overrides merge
on top of the built-ins instead of replacing the whole map, and let a
`null` value remove a key. The default build output is unchanged.
Add a regression test and update the Sass and Theme docs.
Fixes#42847
* Use var(--black) in theme config test to satisfy color-named lint
The stylelint color-named rule rejects named colors like `black` in
declaration values. Reference the token instead, which also matches how
real theme maps set values.
* fix(datepicker): close the popup when focus leaves
Vanilla Calendar Pro ignores focus, so keyboard users could
tab out and leave the calendar open. Dismiss it on document
focusin outside the trigger and popup.
* chore: drop generated dist from the datepicker focus fix
Keep the source, tests, and docs. Rebuild dist on merge.
* refactor(datepicker): cut the focus-dismiss comments
Keep one note on why the listener is on document. Drop the rest.
* docs(homepage): add a For Agents menu
Give agents a homepage path to our skills and llms.txt.
The menu copies the install command and opens ChatGPT or Claude.
* style(docs): format the For Agents menu with Prettier
Convert the remaining plain !default map literals to the defaults()
two-step pattern, so `@use ... with (...)` merges overrides on top of
the built-ins and a null value removes a key. This matches every other
token, size, and variant map in the codebase.
Covers $spacers, $negative-spacers, $sizes, $radii, $border-widths,
$container-max-widths, $position-values, $aspect-ratios, $font-weights,
$color-tints, $color-shades, and $badge-variants. The default build
output is byte-identical.
Add a regression test that merges config maps through the entrypoint.