> For the complete documentation index, see [llms.txt](https://tina-hammar.gitbook.io/tall-forms/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://tina-hammar.gitbook.io/tall-forms/upgrade-v7-v8/styling-changes.md).

# Styling changes

### Merge and review `tall-theme.css`

There might be some small changes to some classes that aren't documented here. Please publish (--force), merge and review the theme before publishing it to production.

### **Blade UI Kit icons**

* Blade UI kit icons, tested with version "^1.1"
* Follow instructions if you made a **custom theme**.
* No custom theme? This change might affect you, if you **republish** the theme.

I have noticed that icon libraries handle the svg css `fill="..."` attribute differently. Some works best with `fill: currentColor` and others with `fill:none`. 

Depending on which icon library you use in your project, **change the `.svg-icon` class** in `tall-theme.css` accordingly.

Due to this, I've updated the `icon()` and `sfxIcon()` field methods to let you add classes. 

The  `.svg-icon` in `tall-theme.css` has also changed accordingly. 

I have added the tailwind css `fill-current` class to the `x-tall-svg`  and `$field->tallIcon` in blade view components, to compensate. (Meaning: it won't affect your current projects unless you republish the theme)

```css
.svg-icon {
    @apply inline-flex align-middle overflow-visible;
    /* fill: currentColor; */
    font-size: inherit;
    margin-top: -0.1rem;
```

### **Checkboxes and Radio** 

Checkboxes and Radio have new wrapper classes, that inlines the options instead of stacking them as before. See the image below.

```css
/*.tf-radio-fieldset, .tf-checkboxes-fieldset */
@apply grid grid-cols-1 sm:grid-cols-2 md:grid-cols-3 lg:grid-cols-4 xl:grid-cols-5;
```

![](/files/-Mgol91rS30ix2f0PqUP)

### Repeater

The buttons are stacked instead of in a row on larger screens to avoid taking up space.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://tina-hammar.gitbook.io/tall-forms/upgrade-v7-v8/styling-changes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.