Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

custom units aren't "preferred" in classes selection

Open
#25 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Mostly clear
Activity status
Stale
Tech stack
tailwindcss
Domain
devtools, frontend

Research direction

Reproduce the provided HTML and Tailwind classes in Chrome with DevTools open at a 2560px window, then compare the applied grid class with DevTools closed. The issue is done when the appropriate min-* class is selected consistently and the base grid-cols class no longer overrides it in DevTools.

Written by the indexing model from the issue text.

Description

I know it's a rare issue, but still, i think it's worth sharing.
Here is a component that displays a certain number of cards according to screen width (hence the precise numbers).

<div class="projects-cards mt-10 grid
                max-w-full
                grid-cols-[repeat(1,_minmax(273px,_1fr))]
                min-[626px]:grid-cols-[repeat(2,_minmax(273px,_1fr))]
                min-[1000px]:grid-cols-[repeat(3,_minmax(273px,_1fr))]
                min-[1356px]:grid-cols-[repeat(4,_minmax(273px,_1fr))]
                min-[1591px]:grid-cols-[repeat(5,_minmax(273px,_1fr))]
                min-[1900px]:grid-cols-[repeat(6,_minmax(273px,_1fr))]
                gap-11 pb-10"
                     id="projects-cards">

                </div>

In the browser without DevTools, the min-* classes have higher priority: if my window width is 2560px, i'll have 6 rows.
But in Chrom with DevTools, the grid-cols-[repeat(1,_minmax(273px,_1fr))] is applied, whatever the actual window width.

Dominant language
No language data
Stars
5
Forks
0
PR merge metrics
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from beyondcode/devtoolsfortailwind-community

All issues in beyondcode/devtoolsfortailwind-community

Similar issues

More DevTools issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.