Repository navigation
Conversation
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info
WalkthroughSelector parsing now treats ChangesSelector parsing
Suggested reviewers: Priority: ➖ Normal Merge Risk: ⚪ Minimal · up to
|
| Check name | Status | Explanation |
|---|---|---|
| Linked Issues check |  |
Check skipped because no linked issues were found for this pull request. |
| Out of Scope Changes check | |
Check skipped because no linked issues were found for this pull request. |
| Title check | |
The title clearly and concisely describes the main change: parsing ::details-content and ::picker() like ::part(). |
| Description check | |
The description explains the problem, fix, scope, compatibility considerations, and verification results. It does not use the exact template headings, but it provides the required information in equiv… |
Full details: Description check
-
Explanation
The description explains the problem, fix, scope, compatibility considerations, and verification results. It does not use the exact template headings, but it provides the required information in equivalent sections.
- Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.
Comment @coderabbitai help to get the list of available commands.
Collaborator
Author
|
Updated 6:05 AM PT - Oct 17th, 2026
❌ @robobun, your commit ec19fa5 has 1 failures in
🧪 To try this PR locally: bunx bun-pr 45504That installs a local version of the PR into your bun-45504 --bun |
Collaborator
Author
|
Status: landed on main in #47025 (7942008). This PR is closed. How I reproduced it printf '::picker(select):popover-open { opacity: 1 }\n' > a.css && bun build ./a.css
printf '::picker(select):is(:popover-open) { opacity: 1 }\n' > b.css && bun build ./b.css
printf 'details::details-content::before { content: "" }\n' > c.css && bun build ./c.css
PR: #45504 |
![claude[bot]](https://avatars.githubusercontent.com/in/1236702?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Nothing blocking. The comments below are optional suggestions. There is no need to push a fix for them before merging.
Beyond the inline findings, I also checked the AFTER_UNKNOWN_PSEUDO_ELEMENT -> HAS_PSEUDO_ELEMENT rework: the old bit's only reader was the SelectorFlags::HAS_PSEUDO computation in parse_selector, and the new bit is set on every Impl::PseudoElement result (known or unknown), so that flag is computed identically. SelectorFlags::HAS_PART is now also set for ::details-content/::picker(), but nothing in src/ reads it today.
Extended reasoning...
The change is confined to src/css/selectors/parser.rs plus tests, reworking the selector-parsing state bitflags so two known pseudo-elements take the ::part() state and loosening the functional-pseudo-class gate after it; it touches no security-sensitive surface. Three inline findings were posted, so a human look is already signalled; this note only records the bitflag rename and the HAS_PART/HAS_PSEUDO consumers I traced and found behavior-preserving.
Additional findings (outside the current diff — GitHub can't attach inline comments there):
-
🟡
src/css/selectors/parser.rs— Users who write::picker(select):first-child,::details-content:root,:empty,:scopeor:hostafter the two names now get a built rule that no browser matches, where 1.4.1 failed the build. In AFTER_PART_LIKE state parse_simple_pseudo_class skips the tree-structural match at src/css/selectors/parser.rs:3699 and falls to parse_non_ts_pseudo_class at parser.rs:3725, which returns PseudoClass::Custom with no warning. The sibling:nth-child(2)is still rejected at parser.rs:3756, so the leniency is inconsistent. Fix: after a part-like pseudo-element, tree-structural names must either be rejected like:nth-child()or at least warn, by checking allows_tree_structural_pseudo_classes before the Custom fallback for those names. [also at: src/css/selectors/parser.rs:3656 - Users ofbun buildwho write::picker(select):has(:popover-open)or::details-content:has(:hover)now get a bundle containing a rule Chrome drops, with no diagnostic, where the base branch failed the build. parse_has at src/css/selectors/parser.rs:3656 has no state gate and copies AFTER_PART_LIKE into child_state at parser.rs:3852, and parser.rs:3733 only restricts pseudo-classes under AFTER_PSEUDO_ELEMENT, so the argument parses.]Why this was flagged
Trigger: a stylesheet containing
::picker(select):first-child {}or::details-content:host {}run throughbun buildor Bun.build. parse_compound_selector at src/css/selectors/parser.rs:787-788 now sets AFTER_PART_LIKE for these names, so allows_tree_structural_pseudo_classes (parser.rs:2678) is false and thefirst-child/root/empty/scope/hostarms at parser.rs:3700-3714 are skipped. The name then reaches parse_non_ts_pseudo_class at parser.rs:3725; lookup_non_ts_pseudo_class (parser.rs:1453) has no such entry, so parser.rs:1333 returns PseudoClass::Custom silently. The selector prints verbatim and the rule is emitted; Chrome drops it. On the base branch these inputs failed the build with InvalidPseudoClassAfterPseudoElement, so a typo or misuse that was caught in 1.4.1 is now shipped silently. The:nth-child()rejection at parser.rs:3756 shows a safeguard exists for siblings but not here. Remedy: in AFTER_PART_LIKE state, reject or warn on tree-structural non-functional names rather than mapping them to Custom.Verification: parse_compound_selector in src/css/selectors/parser.rs (lines 786-791) now inserts
AFTER_PART_LIKEfor these names. In parse_simple_pseudo_class thefirst-child/root/empty/scope/hostarms at lines 3699-3715 are skipped. Control falls to line 3725, where line 1333 returnsPseudoClass::Custom { name }with no diagnostic. By contrast:nth-child(2)is rejected at line 3756.
Collaborator
Author
|
Thanks. My answers to the three findings: Structural pseudo-classes and
|
#41122 made `::details-content` and `::picker()` known pseudo-elements. A known pseudo-element gets the strict state of `::before`: only a user action pseudo-class can follow it. `::picker(select):popover-open` and `::details-content::before` failed the build, and `::picker(select):is(:popover-open)` lost its argument with no diagnostic. 1.4.0 built all three. The two names now set the parsing state that `::part()` sets, so any pseudo-class or pseudo-element can follow them. `::details-content` is an element-backed pseudo-element in css-pseudo-4. `::picker()` is part-like by CSSWG resolution (w3c/csswg-drafts#10758). lightningcss keeps both strict. That state now accepts a functional pseudo-class, so `::part(x):dir(rtl)` parses. `::checkmark` and `::picker-icon` stay strict.
robobun
force-pushed
the
robobun/47fe6f38/css-element-backed-pseudo-elements
branch
from
October 17, 2026 06:44
42fb255 to
405ee89
Compare
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Collaborator
Author
|
|
Jarred-Sumner
added a commit
that referenced
this pull request
Oct 27, 2026
### What does this PR do? Consolidates the open pull requests on the CSS parser (`src/css`: parsing, minifying, lowering, printing, CSS modules) into one. 179 open pull requests were in scope. Each was judged by one rule: **the output must mean to a browser what the input meant.** Every claim was run through a build of `main`, a build with the change, lightningcss 1.33 and Chromium 156 (CSSOM, computed values, painted pixels for colors and gradients), and counted against 10,116 real stylesheets: the published CSS of about 190 popular npm packages, plus stylesheets from open source repositories. 107 land here, whole or in part, most of them cut down. The source diff is net negative. Of the 10,116, 9,509 are stylesheets that someone ships. The rest are test fixtures of other tools (521), Tailwind v4 source that needs its plugin (59) and SCSS, PostCSS or template source (27). | 9,509 shipped stylesheets | `main` | this branch | |---|---|---| | fail to build | 71 | 35 | | ... of those, valid CSS that Bun rejects | | 0 | | minified output reads differently in Chromium than the input | 552 | 2 | | CSS modules with a name that is referenced but not defined, or exported but not defined | 166 | 0 | | all 10,116 | `main` | this branch | |---|---|---| | fail to build | 192 | 141 | | minified output reads differently in Chromium than the input | 593 | 15 | | build on `main`, fail here | | 0 | | right on `main`, wrong here (minified, and at the default targets) | | 0 | | size of the minified output, no targets | 162.32 MB | 162.47 MB (+0.093%) | | size of the output at the default targets | 224.1 MB | 210.2 MB (-6.2%) | A syntax error is a build error, with one exception: the IE star hack `*zoom: 1` is skipped, because tachyons and handsontable ship it. The 35 shipped stylesheets that fail are invalid CSS: 28 have a selector that Chromium drops (semantic-ui-css, swiper, @ionic/core, Adobe Spectrum, xp.css), 2 an `@import` after other rules, and one each `@supports not X and Y`, a nested `@keyframes`, a stray comma, a selector list in `::slotted()`, `@media screen\0` (govuk-frontend). The 2 that read differently fold a `color-mix()` inside a gradient (see the known gaps). The growth of the minified output is rules and declarations that `main` deleted by mistake: 87 KB of rules, 45 KB of prefixed declarations that only browser targets can rule out. #### Popular CSS that `main` breaks today - normalize.css, modern-normalize, sanitize.css: `font-family: monospace, monospace` is collapsed to `monospace`, which changes the font size from 16px to 13px (#46662). - CKEditor 5, Tabler, Carbon, VitePress, Ionic, PatternFly, Excalidraw: a rule of custom properties is deleted as a "duplicate" of a later rule with the same selector and other custom properties. 37 stylesheets lose 1,681 custom properties (#33684). - Material Components, daisyUI, DocSearch, plyr: a `var()` size loses to its own fallback (#42101). - nextra, daisyUI, CKEditor: declarations written after a nested rule are moved above it (#45462). - antd 4, purecss, govuk-frontend: browser hacks in selector lists start to apply everywhere (#42100). - foundation-sites, flatpickr, 98.css, blueprintjs, scalar, react-datepicker: the build fails on valid CSS (#46756, #38552, #38534). tachyons, handsontable: it fails on the IE star hack (#46751). - nodejs.org, Mantine: a CSS module exports classes that no rule defines, because the `@apply` or `@mixin` in them is moved out of the rule (#46759). - hint.css and 42 more: `z-index: 1000001` and `1000000` become the same number (#46715). - Adobe Spectrum: `--version: 5.0.1` prints as `5.1`. - A quarter of all stylesheets: minified output has a stray space in `align-items: center` (#41993). #### Behavior changes to look at first 1. **`light-dark()` is kept as written at the default browser targets** (#42009). The lowered form `var(--buncss-light, a) var(--buncss-dark, b)` is invalid unless a compiled `color-scheme` covers the element: 184 of the 215 real stylesheets that get it never define the variable, so every browser drops the declaration. The docs section on the polyfill is removed. 2. **`border` is not built from longhands** (#42072): `border-width:0;border-style:solid;border-color:red` stays three declarations, because `border` also resets `border-image`. 305 real stylesheets grow by 30 KB in total; `bootstrap.min.css` by 113 bytes, 5 gzipped. No real stylesheet was found where the old merge shows, so this is the one to drop if size matters more. 14 existing expectations change. 3. **A CSS module no longer exports names that only occur inside `:global(...)`** (#45487). 73 real modules lose 202 export keys, all of them names that no rule has. `import { g }` or `composes: g` of such a name becomes a build error. 4. **Container names and `@counter-style` names stay global in a CSS module** (#45247 by @mikamikasuki). `main` hashes the `@container` name but not `container-name`, so a named query never matches. postcss-modules (Vite, css-loader, Next.js) keeps them global; lightningcss and esbuild hash both. Global keeps a container that is queried from another file or from JS working. 5. **Syntax errors are build errors, also two that `main` lets through**: a media query that stops short (`@media screen and {`, `@media not {`, `@import "a.css" screen and;`) and `@media (width <) foo {`. No stylesheet of the 10,116 has either. A condition that is valid by the grammar though no browser knows it, `( ... )` or `fn( ... )`, is kept as written (#46756): `(min-width:0\0)`, `(not(hover))`. 6. **Declarations after a nested rule stay where they were written**, as a nested declarations rule (#45462). Changes the output of 199 real stylesheets; in a fuzz of 2,850 nested programs compared by computed style, `main` was wrong in 1,056 and the pull request's code, before it was trimmed here, in none. 7. **`Bun.color`**: `color()` inputs are converted instead of returned as a string (`Bun.color("color(srgb 1 0 0)", "hex")` was `"color(srgb 1 0 0)"`); `currentColor`, system colors and `light-dark()` give `null` in the converting formats instead of the keyword as a string; a relative color or `color-mix()` outside sRGB is clipped, not gamut-mapped (`hsl(from oklch(100% .399 336.3) h s l)` is `#ff5bff`, was `#fff`). 8. The `:-moz-any()` and `:-webkit-any()` copies of rules with `:is()` are gone at the default targets (#45945, #42029). The `:-webkit-any()` copy outranked the original rule: `.title{color:blue} :is(h1,h2,h3){color:red}` painted red. 5.8% of all default-target output was the `:-moz-any()` copies. 9. `Property` grows from 216 to 224 bytes: `Url` stores its text as a slice so that two `url()` values can be compared (#46895). The pull request packed a pointer and a `u32` behind `unsafe` to avoid that. #### Not in this PR, needs a decision - **Raise the default browser targets (#40369) and add a `cssTarget` option (#40368).** Today: Chrome 80, Edge 80, Firefox 78, Safari 14, Opera 67, and no public way to change them. At Vite 8's floor the output of the 9,924 stylesheets is 15.3% smaller (3.9% gzipped). About a dozen fixes here only matter at today's floor, and code for older targets is unreachable without the option. - Vendor prefixes for `user-select`, `appearance`, `hyphens` and five more (#45814): 1,116 real stylesheets lack a prefix they need at the default targets. And for `backdrop-filter` (#44648): 173. - Clip instead of gamut-map in the sRGB fallback of a plain wide-gamut color: deletes about 90 lines, changes every pinned fallback hex. If the mapping stays, #44647 by @oddharsh makes it closer to what browsers paint (colors off by 2/255 or more: 168 to 110 of 3,170 real ones). #### Changes **Rules: duplicates, merging, nesting, fallbacks** - The `:-moz-any()` copy of every rule with `:is()` or `:not(a, b)` is gone: Firefox 78 has `:is()` (#45945). 1,164 real stylesheets - Keep declarations written after a nested rule in place with a nested declarations rule (#45462). 379 real stylesheets - With nesting compiled away, an unknown at-rule inside a style rule was moved out of it: `.wrapper{@apply flex}` printed a bare `@apply flex;` and the rule was gone, so a CSS module exported a class that no rule defines. It now stays in a block under the compiled selector. 72 real modules with Tailwind's `@apply`, 25 with Mantine's `@mixin` (#46759). 316 real stylesheets - Keep !important in the rules generated for logical properties and color-scheme (#38597). 311 real stylesheets - With browser targets, remove an earlier duplicate rule only when its declaration block is equal (#46861). 171 real stylesheets - Compare custom property names in `PropertyId` equality and importance in duplicate-rule detection (#33684). 40 real stylesheets - Keep same-condition @supports rules and empty named @layer blocks (#46733). 31 real stylesheets - Keep target-added vendor prefix passes on cloned and re-minified rules, and never print a bare `:full-screen` (#43339). 12 real stylesheets - Keep the selectors on rules added for color fallbacks and logical properties (#43240). 3 real stylesheets - A later declaration of a property drops the `@supports` color copies of the earlier one, which printed after the rule and won (#45560). 2 real stylesheets - Do not merge style rules in a stylesheet that holds `revert-rule` (#46953). 1 real stylesheets - `@import ... supports(-webkit-mask: none)` kept its prefix (#38589) **Properties and shorthands** - Print align-items:center without a stray space when no safe/unsafe keyword is given (#41993). 3,317 real stylesheets - Emit the physical longhands instead of the inset shorthand for targets without it (#38583). 1,452 real stylesheets - Keep the stops of an upward gradient as written, and drop a `50%` hint only at the midpoint (#46790). 104 real stylesheets - Emit unparsed border-block-* declarations when compiling logical borders (#38582). 89 real stylesheets - Keep repeated font families and dedupe only the inserted system-ui fallbacks (#46662). 88 real stylesheets - A `width` / `height` / `min-*` / `max-*` with `var()` or `env()` was printed before the plain fallback written above it, so the fallback won (#42101). 26 real stylesheets - Keep box-orient and box-direction when flex-direction or flex-flow follows (#45672). 16 real stylesheets - Write held prefixed background declarations at every flush (#46882). 6 real stylesheets - Derive equality for Size2D and BorderRadius, and keep every prefix in the border-radius handler (#45665). 2 real stylesheets - Print `none` instead of an empty border-image, mask-border or mask-box-image value (#45143). 2 real stylesheets - Keep font/transition sub-properties on the side of the shorthand they were written on (#41990). 2 real stylesheets - CSS-wide keywords are not names: `font:12px Arial;font-family:inherit` printed `font:12px inherit`, `color-scheme:inherit` and `color-scheme:auto` printed `normal`, `transition-property:unset` was folded into `transition` (#42022). 2 real stylesheets - Only fold font longhands into `font` when the rule declared a `font` (#45459) - Keep a font family name quoted when its identifiers do not read back as the same name (#46606) - Stop rewriting valid positions into ones browsers reject (#45197) - `border` is no longer built from longhands unless the rule also sets what `border` resets (`border-image`), and an author's `border-image` reset is no longer dropped. `transition` is likewise only written where the rule wrote one, because it resets `transition-behavior` (#42072) - `border; border-image: <gradient>; border-image-slice: 1` lost the gradient in every default build (#42018) - A prefixed `linear-gradient` keeps its direction, written or generated: the prefixed syntax names the starting side and measures angles differently (#46697) **At-rules** - Print @font-face format() keywords as strings (#37979). 439 real stylesheets - Print @supports `not` conditions without a leading space (#38559). 88 real stylesheets - Reset after the number token of a unicode-range (#45835). 33 real stylesheets - Keep `<general-enclosed>` media and container conditions as written (#46756). 24 real stylesheets - A strict range such as `(width < 768px)` lowered for old targets still matched at exactly 768px. The step is now `.02px`. The `not all and` form for other units is not taken (#46806). 18 real stylesheets - Keep scanning an @supports condition after a nested block (#38552). 9 real stylesheets - Every `@counter-style name` printed as `@counter-stylename`, which browsers drop (also #46692). In a CSS module the name now stays global, like the `list-style` that refers to it (#33679). 9 real stylesheets - Keep a keyframe whose block has an invalid item (#46288). 2 real stylesheets - Read an @Property initial-value on the stylesheet's parser, keep an unmatched value as written (#45806). 2 real stylesheets - `@media {}` is `all`. A media query that stops after `and`, `or` or `not` (`@media screen and {`) is a build error; `main` printed `not all` or dropped the condition, silently. The `@layer` and type selector parts are not taken (#46869). 2 real stylesheets - Accept a name-only `@container` and a `style()` feature with no value (#46689). 1 real stylesheets - Parse `<timeline-range-name> <percentage>` keyframe selectors (#45652) - Allow `or` inside parentheses after a media type (#45088) - Print the `=` comparison in media and container queries as `=` (#45071) - Parse the @font-palette-values font-family descriptor as a list of family names (#45484) **Selectors** - Never wrap a selector list in :is() (#46787). 414 real stylesheets - Stop emitting :-webkit-any() copies of :is() that outrank the original rule (#42029). 373 real stylesheets - With browser targets, a selector list with a vendor-prefixed member was split, which revives hacks that rely on other engines dropping the whole list: `.s *::-ms-backdrop,.s{flex:auto}` applied everywhere. Rewritten; the list is printed as written (#42100). 42 real stylesheets - Print the vendor prefix on downleveled :any-link, :read-only, :read-write, :placeholder-shown and :autofill (#42131). 12 real stylesheets - Fix nesting lowering of a `&` that does not lead its selector (#43047). 8 real stylesheets - `@scope`: `&` and implicit selectors compile to `:where(:scope)`, relative selectors and bare declarations parse (#43165). 7 real stylesheets - Only reject bare :global / :local pseudo-classes in CSS modules (#38534). 5 real stylesheets - Stop truncating `@scope to (...)` and stop replacing `&` in the scope-end selector (#43146). 2 real stylesheets - `[xl|href$=".pdf"]` lost its namespace prefix (#45159). 2 real stylesheets - Match An+B keywords exactly and take only `+` as the leading sign (#42953). 1 real stylesheets - Parse ::details-content and ::picker() like ::part() (#45504). 1 real stylesheets - Parse :window-inactive as an ordinary pseudo-class, and accept it after ::selection (#45815) - Print :nth-col(1) and :nth-last-col(1) in functional form (#41575) - `li::before::marker` failed the build (#45810) - `&` inside `:nth-child(... of S)` is resolved when nesting is compiled away. The second selector serializer (326 lines) is deleted (#43024) **Colors and `Bun.color`** - Keep light-dark() as written under the default browser targets (#42009). 227 real stylesheets - Number and percentage channels parse in `lab()`, `lch()`, `oklab()`, `oklch()`, `hsl()` and `hwb()`; the hue of `lch` / `oklch` is no longer scaled by alpha (#45084). 130 real stylesheets - `Bun.color` returns `null` for `currentColor`, system colors and `light-dark()` in the converting formats, instead of the CSS keyword as a string (#33047). 130 real stylesheets - Relative colors: channel keywords are on the scale of their function (`rgb(from #369 calc(r + 10) g b)`), the origin's alpha is kept, a relative color kept as written gets no `@supports` copies, and a result outside sRGB is not folded (#45362). 31 real stylesheets - Keep rotate: 0deg out of none, and keep the origin alpha in relative colors (#38486). 13 real stylesheets - Compute the D50 reference white in f32 so greys convert to lab(l 0 0) like lightningcss (#38535). 7 real stylesheets - Return a missing hue for a grey from conversions into lch, oklch, hsl and hwb (#45201). 5 real stylesheets - Fix color(a98-rgb), srgb-linear relative colors and color-mix(in xyz-d50) (#38487). 4 real stylesheets - Match named colors without regard to ASCII case (#45092). 3 real stylesheets - Fold min(), max() and clamp() over plain numbers (#39515) - `calc(l - .08)` in a percentage channel of a relative color became NaN and printed `#000` (also #45970) (#45971) - Bun.color: convert color() inputs instead of returning them as a CSS string (#38488) - A `color-mix(in srgb, ...)` result outside sRGB prints `color(srgb ...)` instead of a gamut-mapped hex (#39269) **`calc()` and numbers** - Rounding to 6 significant digits ate into the integer part: `z-index:2147483647` became `2147480000`, `max-width:9999999px` became `10000000px`, `--x:1234567.5` became `1234570`. It now only cuts a fraction short: a value kept as tokens prints its source text, a typed value prints every integer digit and at least one digit of the fraction (#46715). 43 real stylesheets - A number without a unit is no longer repaired into `px` (`height:1.5715` is dropped by a standards-mode browser, so it prints as written), `calc(-1 * 0)` is not a length, and on a property of the range [0,∞] (sizes, border radii, padding, border and outline widths, gap, `flex-basis`, `font-size`) a `calc()` that folds below zero prints `0` instead of an invalid negative literal, and a negative literal no longer replaces the valid declaration before it (`width:10px;width:-5px` printed `width:-5px`) (#42104). 24 real stylesheets - Print numbers from the f32's shortest digits, not its f64 expansion (#38565). 17 real stylesheets - Print negative numbers below 1 with a single minus sign (#38516) - Keep math functions over two different length units as written (#38489) - Fold rem() with a truncated quotient, so it keeps the sign of the dividend (#32286) - A one-argument `min()` / `max()` around a sum printed without any function (`width:100% - 20px`) (#46145) - `round()` breaks ties upward and handles a negative step as browsers do (#45249) **CSS modules** - A CSS module exports its `@keyframes` names (`styles.spin`). Hashing is unchanged (#46720). 145 real stylesheets - A name inside `:global(...)` prints plain but was exported as `name_<hash>`, a class no rule has (also #38573) (#45487). 90 real stylesheets - Keep container names global in CSS modules (#45247). 6 real stylesheets - Tag the keyframes name when an `animation` value falls back to raw tokens (#46034). 6 real stylesheets - In a plain stylesheet `composes: a from "./b.css"` was treated as an import: the file was inlined and an absolute path printed (#45961). 4 real stylesheets - Drop a rejected composes instead of failing the file at print time (#38538). 1 real stylesheets - Keep every rule's custom properties for the composes conflict check (#38523) - Keep composes working after a nested rule in the same block (#38520) - `IdentOrRef::hash` read 2 of 16 bytes, so in release builds every class of a module hashed alike (#30784) **Tokens, `url()`, diagnostics** - The block skip stack no longer allocates on every block exit (#39533) - Report the diagnostic's line without its line breaks in position.lineText (#38342). 192 real stylesheets - Compare `url()` values by their text (#46895). 26 real stylesheets - Values kept as tokens keep the blanks they were written with instead of having them re-invented at print time: `attr(x type(<number>))` printed `type(< number> )`, which browsers drop. Minified output still drops the blanks that cannot matter (#45577). 19 real stylesheets - The IE star hack (`*zoom:1`) failed the whole build. The declaration is skipped, as every browser does. It is the one syntax error that builds: tachyons, handsontable and jasmine ship it (#46751). 8 real stylesheets - The path of a copied asset spliced into `url()` is always quoted, so a file name with a space or a parenthesis cannot end the `url()` (#41557). 7 real stylesheets - Move the skip loop of parse_until_before out of the generic body (#39520) - Remove dead code from bun_css: the unused `impl Default for Property` (#45618) - Default the at-rule and qualified-rule parser traits, drop the url_to_css shim (#31999) **Speed** Four inputs that took quadratic or exponential time, or produced output out of proportion, are now linear, with no new limit and no extra pass (#31639, #42243, #38531, #43421). **Tests only** - `css-fuzz.test.ts` never ran in CI and timed out on debug builds; it is a deterministic table now (#38500) - `nth-anplusb-ident.test.ts` counts heaps in a child process (#46331) - `color.test.ts` checks the ansi-16 sweep with one `expect()` (#42824) - Not CSS, but it failed this PR's CI and fails on `main` too: `ws-proxy.test.ts` on Windows, "a message sent during a TLS renegotiation arrives after it". The helper server now renegotiates from the callback of the frame's write (#46170) **No pull request covered these** - `--v: 5.0.1` printed as `5.1`, `--w: 1.0.0` as `10`, `--x: 1+2` as `12`, `2n+1` as `2n1`: a number token that touches another keeps its source text. - `color-scheme: auto` printed as `normal`, and `color-scheme: dark light` as `light dark`. - A bare `:global` or `:local` in a CSS module sets the scope of the names after it, up to the end of the selector, as in css-loader. It was a build error. - The scrollbar states (`a:horizontal`, `::-webkit-scrollbar{&:horizontal{}}`) are valid in a plain compound, as in WebKit and Blink. - Without browser targets, `-webkit-box-align`, `-ms-flex-align` and the like were dropped next to their standard form (flatpickr, foundation-sites, materialize-css: 28 stylesheets), and `-webkit-fill-available` before `-moz-available` (beercss). - `(-o-min-device-pixel-ratio: 2/1)` printed as `2`. - `sin()`, `cos()` and `tan()` are exact at multiples of 90deg: `calc(100px * cos(90deg))` printed `-.00000437114px`. - A `display-p3` color at targets that have P3 but not the other `color()` spaces (Safari 10.1 to 14) got itself as a fallback. - `width: rem(-18px, 5px)` folds to a negative literal once `rem()` is right; it prints `0`. - Consecutive nested declarations rules, which arise when same-query `@media` blocks in one rule merge, are folded into one and count against the existing selector expansion limit as the `&{}` rules they replace did. #### Known and not fixed here - Four longhands are still folded into a `transition` the author did not write where the targets add a prefixed copy of a property (`mask-image` at Chrome 80): only the shorthand gives the copy its own times. - A later `background`, `box-shadow` or `border-*` declaration still loses to the `@supports` copy of an earlier `var()` value of the same property with a wide-gamut color. Same on `main`; #45560 is taken for the properties of the fallback handler and for unparsed values only. - A merged rule prints the unprefixed name in the passes of the rule it absorbed: `.d::-webkit-input-placeholder{}.d::-moz-placeholder{}` prints `::placeholder` for the second (#42106, not taken: it breaks the merge of prefix-equivalent rules). - The `border`, `outline` and `font` shorthands, `line-height`, `scroll-padding`, `background-size` and a few more still print a `calc()` that folds below zero as a negative literal. No real stylesheet has one. - `all` is not a property Bun knows, so `a{margin-top:1px;all:unset}` prints `all` first. Same on `main`. - A selector kept as raw tokens loses the blank before `*` when minified: `--sel: .dark *` prints `.dark*`. Same on `main`. - `width:calc(0% + 12px)` folds to `12px`, which lays out differently in a table cell. Same on `main`. - The `:dir()` / `:lang()` rules of a lowered logical property print before the nested rules of their rule, so a logical declaration written after a nested rule of equal specificity still loses to it. Same on `main`. - A fraction is still rounded to 6 significant digits (`12345.678` prints `12345.7`, `33.3333333333%` prints `33.3333%`). Keeping every digit would add up to 282 KB over the corpus. - `@keyframes "quoted"` is hashed in a module but not exported. - In a module, a keyframes name inside a `var()` fallback is not hashed: `animation: var(--enter, fade 1s)`. Same on `main`. - A `color-mix()` or relative color folded to a hex inside a gradient changes the interpolation from Oklab to sRGB (VS Code, clawhub). Printing `color(srgb ..)` instead needs a fallback for `mask-image`, `list-style-image` and custom properties at the default targets, which have none. - A comma list in `@container` still fails the build. - After a bare `:global`, names that are hashed at print time (`::view-transition-old(foo)`) are still hashed; inside `:global(...)` they are not. #### Pull requests in scope that do not land here - Duplicates of a pull request that lands here: #36961 (of #37979), #38478 (of #46662), #38480 (of #46733), #38482 (of #46715), #38491 (of #38500), #38508 (of #45201), #38513 (of #45362), #38573 (of #45487), #38640 (of #38500), #45525 (of #45247), #45589 (of #46756), #45970 (of #45971) - Already fixed on `main`: #38674 - Right, but for input nobody writes (0 of 10,116 stylesheets, and not new syntax): #31916, #38526, #38592, #39349, #41139, #41801, #42042, #42484, #43078, #45604, #45908, #46086, #46221, #46224, #46273, #46694, #46707, #46737, #46755, #46816, #46870, #46934 - Right or harmless, but not worth their code, their bigger output or the behavior they change: #30905, #31924, #33332, #34426, #36225, #38006, #38512, #38547, #38551, #38561, #38572, #38576, #38607, #38623, #38667, #38692, #42106, #42912, #42918, #43407, #43434, #44700, #45442, #45546, #45747, #45759, #45825, #45946, #46061, #46127, #46206 - Need a decision (see above), stay open: #40368, #40369, #44647, #44648, #45814 - Stays open: #45787 Out of scope: CSS linking and chunking in the bundler, the dev server, docs-only pull requests, and repository-wide sweeps that touch `src/css` in passing. Thanks to @mikamikasuki (#45247), @alii (#39520, #31999) and @oddharsh, whose measurements on #40369 and #41990 were used. Fixes #16727. Fixes #24770. Fixes #30772. Fixes #44704. Fixes #45089. Fixes #45237. Fixes #46872. ### How did you verify your code works? - The 35 CSS test files pass on a debug build, also with `FORCE_COLOR=1`. 600+ of the tests in this branch fail on a build of `main`. An earlier head of this branch passed all 179 CI jobs that ran. - The reproduction of each issue listed above was run on `main` (wrong) and on this branch (right). - Differential run over the 10,116 stylesheets, `main` against this branch, minified without targets and through `Bun.build` at the default targets: no stylesheet that builds on `main` fails; Chromium 156 compares the output with the input rule by rule (CSSOM, then computed values on a sized element in a standards-mode document, colors as painted pixels in sRGB and P3). The comparison has 195 control pairs that must read equal or different. For stylesheets that read differently on both builds, mostly because of lowering, the sets of differences were compared; the three new ones are two minifier fixtures that are wrong on both and one comparison artifact. - CSS modules are checked for consistency instead, since hashed names defeat the comparison: every reference points at a name the output defines, every export exists. - `Bun.color`: 59 inputs in 13 formats on both builds; every changed cell was read.
Collaborator
Collaborator
Author
|
Thanks. I ran the original report against a debug build of main at 7942008:
One difference from this PR: on main, a structural or unknown pseudo-class after the two names ( |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
bun buildfails on::picker(select):popover-openand::details-content::beforewitherror: Invalid selector. Invalid pseudo-class after pseudo-element.::picker(select):is(:popover-open)builds as::picker(select):is(), which matches nothing. 1.4.0 built all three.parse_compound_selector(src/css/selectors/parser.rs:786) gives a known pseudo-element the strict state of::before.Fix
PseudoElement::parses_as_element_backed()names the two. They set the state of::part(), renamedAFTER_PART_LIKE. No gate has a per-name exception.::part(x):dir(rtl)builds.::checkmarkand::picker-iconstay strict, as in Chrome.test/js/bun/css/css.test.ts,test/bundler/css/forms-pseudo-elements-41120.test.ts,test/bundler/css/css-modules.test.ts(60 fail on main). Alsotest/js/bun/css/,test/bundler/css/.::details-content,::picker(),::checkmarkand the carousel selectors warn as invalid #41120.Background
SelectorParsingStateis the bit set the parser fills while it reads a selector. Gates test it to decide what can follow.::details-contentis element-backed in css-pseudo-4: any pseudo-class or pseudo-element can follow it.::picker()is part-like by CSSWG resolution ([css-ui] Pseudo-element for select's UA popover w3c/csswg-drafts#10758).::picker(). A maintainer must confirm the::picker()arm.Downsides
::picker(select) optionand::checkmark:checkedbuilt with a warning on 1.4.0 and stay errors. Chrome drops them.::part(). Chrome drops them.parse_selectorinstructions per selector (qemu, main vs PR):.c407 -> 408,.c::before597 -> 598. Release text: -256 bytes.Notes
Origin. No tracker issue reports the refusal. A fuzz run found it and a maintainer chat thread carried the report. Related to #41120 (the warning for these names) and #41122 (made them known, shipped in 1.4.1). The report asked for an exception for four names. This PR changes two:
::checkmarkand::picker-iconare fully styleable pseudo-elements in css-forms-1, not element-backed.The
::picker()question. css-pseudo-4 does not mention::picker(), and css-forms-1 does not call it element-backed yet. The basis is the resolution in w3c/csswg-drafts#10758 ("::picker(select)is a part-like pseudo-element") and the one in w3c/csswg-drafts#10775 ("don't create a special exception to not parse:popover-openon::picker(select)"). #10775 is still open on whether it matches. Blink and Gecko parse it like::part(). WebKit takes only user-action pseudo-classes after it. The lightningcss author wrote on::picker(select):not(:popover-open): "I don't see anything in the spec that says this is valid, and it violates the usual rules of CSS." Bun differs here because 1.4.0 built these sheets. If the answer is no,parses_as_element_backed()keepsDetailsContentonly.Versions (
bun build, Chrome 153.0.8010.52CSSStyleSheet.replaceSync):::picker(select):popover-opendetails::details-content::before::picker(select):is(:popover-open):is()::part(x):dir(rtl),:lang(en),:state(y)::checkmark:checked,::picker-icon:disabled::picker(select) option,::details-content > *,::picker(select).x::slotted(x)::details-content:open::before::marker,::selection:window-inactiveEvery "builds" cell of 1.4.0 came with the
Unsupported pseudo-class or pseudo-elementwarning.Not fixed here. Each of these fails the same on 1.4.0:
::markerafter::beforeand::after. css: accept::markerdirectly after::beforeand::after#45810 adds it, and the two PRs merge with 0 conflicts.:window-inactiveoutside::-webkit-scrollbar*.::slotted(x)::details-content,::slotted(x)::picker()and::slotted(x)::file-selector-button. Servo refuses these too.:is(),:where(),:-webkit-any(),:-moz-any(), both@scopelists) still drops what the parser refuses, with exit 0 and no diagnostic.::selection:is(:window-inactive)prints::selection:is().ERROR:rows are the first live tests of that for these gates. Whether the gates warn and keep the rule is a separate decision.Taken from Servo. Only the
AFTER_PART_LIKEstate and theafter_partparameter of theselectorscrate (servo/stylo@a6101dbd6e, servo/stylo@f9599dc750). parcel-bundler/lightningcss#1308 ports the same model and is not merged. In CSS modules,:global()and:local()after::part()and the two names stay an error:.a::part(x):global(.g)would print.a::part(x).g.Considered.
::part(x):dir(rtl)stays refused.::picker(select).xand::picker(select) > a, prints.a_hash::picker(select).gin CSS modules, and undoes css: recognize ::details-content, ::picker(), ::checkmark and ::picker-icon #41122.Overlaps.
allows_custom_functional_pseudo_classes. A 3-way merge of itsparser.rsover this one has 0 conflicts. Its two readers ofSelectorFlags::HAS_SLOTTEDandHAS_PARTkeep working: both writes stay, andHAS_PARTis now also set for the two names.parser.rshunks fails to apply. It must classify its 5 newPseudoElementvariants inparses_as_element_backed(), and itsis_state_after_partexemption becomes dead. This PR should land first.ꡆ does not touchparser.rs.&inside :global() #45487 changes the signature ofparse_non_ts_functional_pseudo_classtoo: it passes the parsing state. The two PRs conflict in 2 small hunks. The one that lands second readsAFTER_PART_LIKEfrom that state.Measurements (release builds of 116dd64 and of 116dd64 with this diff):
parse_selectorinstructions per selector (qemu, main vs PR):.c407 -> 408,.c:hover629 -> 630,.c::before597 -> 598,.c::before:hover811 -> 812parse_selector: 20,711 bytes, 4,296 instructions (main 20,775, 4,313). Release text: -256 bytes.SelectorParsingState: 11 of 16 bits, 2 bytes (main 11, 2).SelectorFlags: 3 flags (main 3)..c5.19 -> 5.19,.c:hover5.18 -> 5.18,.c::before5.16 -> 5.16. Per kept:is()argument: +1.99."fails" counts rules that Chrome keeps and
bun buildrefuses. "lenient" counts rules that Chrome drops andbun buildprints. The 11 newly lenient rows are:first-child,:only-child,:first-of-type,:root,:empty,:scope,:host,:unknown-thingand:unknown-fn(x)after::picker(select), and::details-content:first-childand::details-content::before:hover.Tests.
test/bundler/css,test/js/bun/cssandtest/bundler/esbuild/css.test.ts: 2851 pass, 4 fail. The 4 are thecss-fuzz.test.tstests, which pass their 5 s and 10 s limits only on a release build.test/bake/dev/css.test.ts: 15 pass.::slotted(x)::details-content, and the deletion ofSelectorFlags::HAS_SLOTTEDandHAS_PART. It also asked for a short note on css: the pseudo-element table trails lightningcss, so::details-content,::picker(),::checkmarkand the carousel selectors warn as invalid #41120 for the users who follow that issue. I did not post one.