[RasmusDWN]

Flowbite::Toast renders a close button but gives no way to customize it, so apps can't wire up dismissal (or anything else) without overriding the template.

This extracts the button into a Flowbite::Toast::CloseButton component and adds a button slot, following the pattern Card uses for its title:

• Toast::CloseButton holds the button's classes, type, aria-label and icon. Options passed to it are merged over the defaults, like Card::Title.
• Toast gets renders_one :button. When the slot isn't used, it falls back to default_button, rendered with the options from button: {options: {...}}.

Passing options to the default button:

Flowbite::Toast.new(message: "Saved", button: {options: {data: {action: "toast#dismiss"}}})

Rendering your own button:

<%= render(Flowbite::Toast.new(message: "Saved")) do |toast| %>
  <% toast.with_button do %>
    <%= render(Flowbite::Toast::CloseButton.new(data: {action: "toast#dismiss"})) %>
  <% end %>
<% end %>

[Copilot]

🟡 Changes recommended

Flat aria-label options produce duplicate attributes rather than reliably overriding the default accessible label.

1 open issue

• Prevent duplicate aria-label attributes when using flat labels · New

What changed in this PR

This PR lets applications customize the Toast close button without overriding its template, using the nested options pattern already used by InputField.

Changes:

• Adds close_button: {options: {...}}, merging HTML options with defaults and appending custom classes.
• Renders the button through Rails’ tag helper.
• Adds customization tests and documents the new option.

File	Description
test/​components/​flowbite/​toast_test.rb	Tests custom classes, data attributes, and nested ARIA labels.
CHANGELOG.md	Documents close-button HTML options.
app/​components/​flowbite/​toast/​toast.html.erb	Renders the close button with merged options.
app/​components/​flowbite/​toast.rb	Adds close-button configuration, default classes, and option merging.

_{Review effort: Balanced}

[Copilot]

🟡 Changes recommended

Option merging can remove the button’s accessible name, and class replacement conflicts with the stated append behavior.

2 open issues

• Preserve default aria-label when merging ARIA attributes · New
• Merge custom button classes with default classes · New

1 resolved since last review

• Prevent duplicate aria-label attributes when using flat labels

_{Review effort: Balanced}

[Copilot]

🔵 Needs a closer look

Custom ARIA options can remove the icon-only close button’s default accessible name.

No open issues 🎉

2 resolved since last review

• Merge custom button classes with default classes
• Preserve default aria-label when merging ARIA attributes

_{Review effort: Balanced}

[koppen]

Given that we don't really know what the button is used for (since we aren't the ones adding behavior to it), perhaps the slot should just be called button? The default button could still be a CloseButton, though.

[RasmusDWN]

I have renamed the slot and argument to button, so now it's more generic. CloseButton is still the default.

[Copilot]

🟡 Changes recommended

The advertised public API and examples must be reconciled with the implemented keyword and slot names.

1 open issue

• Reconcile close button API names across implementation and documentation · New

_{Review effort: Balanced}

[koppen]

🤘