Skip to content

max-w-* malfunction? #15348

@flowtitude

Description

@flowtitude

What version of Tailwind CSS are you using?

Tailwind 4.0 Beta 6

What build tool (or framework if it abstracts the build tool) are you using?

WordPress

I'm not sure if it's a bug, but it used to work fine with the first betas, I don't know if it's since beta 4 maybe. I'm defining in @theme some flexible spaces with a terminology --spacing-4xs, spacing-3xs up to the spacing-4xl value, the problem is that max-w-4xl is taking the value of spacing-4xl in the latest betas, I think it would be more correct to take it from --container-4xl, or am I wrong, if this is correct how could I define semantic type spaces without interfering with max-w-*? thanks for the effort, this is looking great ;-)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions