Skip to content

Enable lightningcss scroll navigation drafts so :target-current parses #20515

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.

Sign up for GitHub

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

Open
aceeyz wants to merge 1 commit into
base: main
Choose a base branch
from
+2 −0
Open

Enable lightningcss scroll navigation drafts so :target-current parses #20515

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0

### Fixed

- Don't warn about `:target-current`, `:target-before` and `:target-after` pseudo-classes when optimizing CSS
- Ensure watch mode detects changes to symlinked `@source` files whose real paths aren't otherwise scanned ([#20356](https://github.com/tailwindlabs/tailwindcss/pull/20356))
- Ensure custom variants using `@scope` wrap the generated utilities instead of nesting inside them ([#20369](https://github.com/tailwindlabs/tailwindcss/pull/20369))
- Fix flattening of `@scope` at-rules ([#20369](https://github.com/tailwindlabs/tailwindcss/pull/20369))
Expand Down
1 change: 1 addition & 0 deletions packages/@tailwindcss-node/src/optimize.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -39,6 +39,7 @@ export function optimize(
inputSourceMap: map,
drafts: {
customMedia: true,
scrollNavigationControls: true,

@greptile-apps greptile-apps Bot Sep 25, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Warning behavior lacks test coverage
The new option is intended to stop warnings for :target-current, :target-before, and :target-after, but the optimizer has no direct test of its warning output. A later change could bring those warnings back without being caught. Please test the warning behavior with both minified and non-minified output.

Knowledge Base Used: Node API and compilation services

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

},
nonStandard: {
deepSelectorCombinator: true,
Expand Down