Open Bobakanoosh opened 4 months ago
Hey @Bobakanoosh can you assign me this issue.
Hello @Bobakanoosh,
Is this issue still active? I would like to work on this.
Best Regards.
Anyone is free to work on this, I'm not a maintained so I cannot assign anyone.
Hi @Bobakanoosh, It's working.
Add this code in tailwind.config file:
screens: { 568: "568px", 768: "768px", 1024: "1024px", 1280: "1280px", },
Example: In tailwind.config
import type { Config } from "tailwindcss";
const config: Config = { content: [ "./src/pages//*.{js,ts,jsx,tsx,mdx}", "./src/components/*/.{js,ts,jsx,tsx,mdx}", "./src/app//*.{js,ts,jsx,tsx,mdx}", ], theme: { screens: { 568: "568px", 768: "768px", 1024: "1024px", 1280: "1280px", }, }, plugins: [], }; export default config;
Re-opening https://github.com/tailwindlabs/tailwindcss/issues/5956, which asks for support for numerically named max-width breakpoints.
It was initially fixed, and then reverted in https://github.com/tailwindlabs/tailwindcss/pull/6289.
What version of Tailwind CSS are you using? 3.4.4
What build tool (or framework if it abstracts the build tool) are you using? N/A
What version of Node.js are you using? N/A
What browser are you using? N/A
What operating system are you using? N/A
Reproduction URL https://play.tailwindcss.com/HZk7pMuTwQ
Describe your issue I personally prefer to use numbered breakpoint names (e.g. 1800, 1200 vs 2xl, xl) as it feels a lot more intuitive during development. This worked with min-width breakpoints, but seems to not work with max-width breakpoints. The playground link documents this issue pretty well.