Permalink
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 12 commits
- 54 files changed
- 7 contributors
Commits on Sep 17, 2024
-
Insert
@defaultsat start of stylesheet (#14427)Prior to this PR, we'd put all of the `@defaults` (the CSS variables and stuff) _after_ the `base` rules. This creates an issue when using `optimizeUniversalDefaults` with CSS that looks like this: ```css @tailwind base; @tailwind components; @tailwind utilities; @layer base { input { @apply shadow; } } ``` …because the default shadow stuff ends up after the base `input` rules, so the generated styles are like this: ```css input { --tw-shadow: 0 1px 3px 0 rgb(0 0 0 / 0.1), 0 1px 2px -1px rgb(0 0 0 / 0.1); --tw-shadow-colored: 0 1px 3px 0 var(--tw-shadow-color), 0 1px 2px -1px var(--tw-shadow-color); box-shadow: var(--tw-ring-offset-shadow, 0 0 #0000), var(--tw-ring-shadow, 0 0 #0000), var(--tw-shadow); } input { --tw-ring-offset-shadow: 0 0 #0000; --tw-ring-shadow: 0 0 #0000; --tw-shadow: 0 0 #0000; --tw-shadow-colored: 0 0 #0000; } ``` This means all of the actual shadow values for the input are reset and the shadow doesn't work. Fixes #14426. Lots of failing tests right because this changes a ton of stuff, albeit in a totally inconsequential way. @thecrypticace if you could update these for me this week that would be a huge help, just banging this fix out quick while the kids are napping 😴 --------- Co-authored-by: Adam Wathan <4323180+adamwathan@users.noreply.github.com> Co-authored-by: Jordan Pittman <jordan@cryptica.me>
3 people authoredSep 17, 2024 < 10000 input type="hidden" name="oid" value="fe48ca83d86690a5f2adf01eb8fc0b02c033c59d" autocomplete="off" data-targets="batch-deferred-content.inputs" /> -
Commits on Sep 23, 2024
-
Improve the performance when checking broad glob patterns. (#14481)
In a large project, it's costly to repeatedly call the function `micromatch.isMatch` that parses a glob pattern, creates a regular expression, and tests the path name against the regular expression. To optimize performance, it's important to cache the parsing and creating process before entering the loop. For example, the content configuration in a project looks like this `['./pages/**/*.{ts,js}', './node_modules/pages/**/*.{ts,js}']`. If the project has 10000 matched files and 10 glob patterns, the function `micromatch.isMatch` will be called 100000 times. --- Co-authored-by: Robin Malfait <malfait.robin@gmail.com> -
Commits on Oct 9, 2024
-
Don't set
display: noneon elements that usehidden="until-found"(……#14625) Fixes an issue reported by the React Aria Components team here: adobe/react-spectrum#7160 Basically `hidden="until-found"` behaves very differently than `hidden` and doesn't actually use `display: none`, so we don't want to apply the behavior we apply for the regular `hidden` attribute. --------- Co-authored-by: Robin Malfait <malfait.robin@gmail.com>
Commits on Oct 15, 2024
Commits on Oct 17, 2024
-
Bump dependencies to fix vulnerabilities (#14697)
This PR fixes some package vulnerabilities that you will see when running `npm install`. This PR fixes that by bumping dependencies to get rid of the vulnerabilities.
-
This PR adds a new `CODEOWNERS` file so that the `@tailwindlabs/engineering` will be automatically requested for review when changes are made to the repository.
-
Commits on Nov 7, 2024
-
Fix config types for boxShadow (#14856)
`boxShadow` accepts multiple shadows just like `dropShadow` does. This patch fixes the TS typings to reflect that. See demo showing that multiple shadows are supported (complete with it incorrectly complaining that the config is bad) here: https://play.tailwindcss.com/VHqWbbEIrz?file=config --------- Co-authored-by: Philipp Spiess <hello@philippspiess.com>
Commits on Nov 14, 2024
-
Add variable fallback to fix Chrome issue (#15003)
This works around an issue in Chrome where `::selection` does not read from variables defined on `::selection` thus breaking all uses of color utilities with the selection variant. e.g. `selection::bg-red-200`. We now add a fallback value of `1` to all uses of `var(--tw-bg-opacity)`, `var(--tw-text-opacity)`, `var(--tw-border-opacity)`, etc… since Chrome treats the variable as if it did not exist because it's not defined on the parent. In Chrome 131 (until the change is rolled back) existing utilities like these will not work: - `selection:text-opacity-50` - `selection:[--tw-text-opacity:0.5]` Fixes #15000 --------- Co-authored-by: Adam Wathan <adam.wathan@gmail.com>
-
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff v3.4.11...v3.4.15