Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add custom breakpoints for screens in extend, resulting in the failure of max-*. #15800

Closed
H-Sven opened this issue Jan 24, 2025 · 1 comment
Closed

Comments

@H-Sven
Copy link

H-Sven commented Jan 24, 2025

What version of Tailwind CSS are you using?

"@nuxtjs/tailwindcss": "^6.12.2"

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

"nuxt": "^3.15.1"

What version of Node.js are you using?

v20.15.0

What browser are you using?

Chrome / Edge

What operating system are you using?

macOS

Reproduction URL

module.exports = {
  theme: {
    extend: {
      screens: {
        'max-lg-inclusive': { 'max': '1024px' },
      },
    },
  },
};
<div
        class="max-lg-inclusive:w-[40rem] relative max-w-[75rem] max-lg:w-[55rem] lg:w-[56rem] xl:w-[75rem]"
      >
</div>

Describe your issue

After configuring like this, max-lg-inclusive:w-[40rem] runs normally, but max-lg:w-[55rem] loses its effect. It does not generate CSS code as expected.

Image Image Image Image

And in VSCode, the Tailwind CSS IntelliSense plugin does not generate prompts like other breakpoints.

@wongjn
Copy link
Contributor

wongjn commented Jan 24, 2025

See #9558.

@tailwindlabs tailwindlabs locked and limited conversation to collaborators Jan 24, 2025
@philipp-spiess philipp-spiess converted this issue into discussion #15810 Jan 24, 2025

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants