An attribute selector inside `:where()`, or a `:is()` of several, never matches: `.test:where([data-test="abc"])` styles nothing
I maintainer di solito rispondono entro 3 giorni
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 3/5
- Tempo stimato
- 1-2 giorni
- Idoneità per principianti
- 74/100
- Tipo di issue
- Bug
- Chiarezza
- Specificata chiaramente
- Stato di attività
- Attiva
- Stack tecnologico
- react-native, typescript
- Ambito
- frontend
Direzione di ricerca
Start in src/compiler/selector-builder.ts, especially parseIsWhereComponents, then read src/native/conditions/container-query.ts to trace how attribute conditions are evaluated. Run the reproducer test src/__tests__/native/attribute-query-in-is-where.test.tsx with the command in the issue. Done when the :where() and multi-selector :is() cases match the element's own attributes while the non-match and single-selector cases still pass.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
Before submitting a new issue
- I tested using the latest version of the library, as the bug might be already fixed.
- I tested using a supported version of react native.
- I checked for possible duplicate issues, with possible answers.
Bug summary
An attribute selector inside :where(), or inside an :is() of more than one selector, never matches: .test:where([data-test="abc"]) styles nothing on dataSet={{ test: "abc" }}, and so does .test:is([data-test="abc"], [data-other="xyz"]). A browser matches both. A single-selector :is([data-test="abc"]) works, because lightningcss flattens it into the rule's own attribute list before the compiler sees it.
The first and third cases fail; the second, a correct non-match, and the fourth pass.
parseIsWhereComponents turns each :is() or :where() branch into a container query, so the attribute test lands on a container query, which src/native/conditions/container-query.ts checks against a container's props rather than the element's own.
Library version
main at 2421ea7 (0.0.0-nightly.2421ea7)
Environment info
System:
OS: Windows 11 10.0.26300
CPU: "(32) x64 AMD Ryzen 9 9950X3D 16-Core Processor "
Memory: 155.26 GB / 255.67 GB
Binaries:
Node:
version: 26.12.1
path: C:\Program Files\nodejs\node.EXE
Yarn:
version: 4.9.2
path: C:\Users\<user>\AppData\Roaming\npm\yarn.CMD
npm:
version: 12.2.1
path: C:\Program Files\nodejs\npm.CMD
Watchman: Not Found
SDKs:
Android SDK:
API Levels:
- "33"
- "35"
- "35"
- "35"
- "36"
- "37"
Build Tools:
- 35.0.0
- 36.0.0
- 36.1.0
- 37.0.0
System Images:
- android-26 | Google APIs Intel x86_64 Atom
- android-28 | Google APIs Intel x86_64 Atom
- android-29 | Google APIs Intel x86_64 Atom
- android-30 | Google APIs Intel x86_64 Atom
- android-31 | Google APIs Intel x86_64 Atom
- android-32 | Google APIs Intel x86_64 Atom
- android-33 | Google APIs Intel x86_64 Atom
- android-34 | Google APIs Intel x86_64 Atom
- android-35 | Google APIs Intel x86_64 Atom
- android-36.1 | Google Play Intel x86_64 Atom
- android-36.1 | Pre-Release 16 KB Page Size Google Play Intel x86_64 Atom
- android-37.0 | Google APIs Intel x86_64 Atom
Android NDK: Not Found
Windows SDK: Not Found
IDEs:
Android Studio: AI-262.9437.185.2621.16467767
Visual Studio: Not Found
Languages:
Java:
version: 17.0.20.1
path: C:\Program Files\Microsoft\jdk-17.0.20.101-hotspot\bin\javac.EXE
Ruby: Not Found
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 19.2.3
wanted: 19.2.3
react-native:
installed: 0.86.3
wanted: 0.86.3
react-native-windows: Not Found
npmGlobalPackages:
"*react-native*": Not Found
Android:
hermesEnabled: Not found
newArchEnabled: Not found
iOS:
hermesEnabled: Not found
newArchEnabled: Not found
Steps to reproduce
- Clone the reproducer branch, which is
mainat 2421ea7 with one file added,src/__tests__/native/attribute-query-in-is-where.test.tsx, and install:git clone --branch repro/541-is-where-attribute-queries https://github.com/YevheniiKotyrlo/react-native-css cd react-native-css yarn install - Run
yarn jest src/__tests__/native/attribute-query-in-is-where.test.tsx.
src/__tests__/native/attribute-query-in-is-where.test.tsx:
import { render, screen } from "@testing-library/react-native";
import { View } from "react-native-css/components/View";
import { registerCSS, testID } from "react-native-css/jest";
test.each([
[".test:where([data-test='abc'])", "abc", true],
[".test:where([data-test='abc'])", "xyz", false],
[".test:is([data-test='abc'], [data-other='xyz'])", "abc", true],
[".test:is([data-test='abc'])", "abc", true],
])("%s on data-test=%s matches: %s", (selector, value, expected) => {
registerCSS(`${selector} { width: 37px; }`);
render(<View testID={testID} className="test" dataSet={{ test: value }} />);
expect(screen.getByTestId(testID).props.style?.width === 37).toBe(expected);
});
Expected: .test:where([data-test="abc"]) and .test:is([data-test="abc"], [data-other="xyz"]) match dataSet={{ test: "abc" }}, as in a browser.
Actual: neither matches.
The run's output on main at 2421ea7, Windows 11, Node 26.12.1
FAIL src/__tests__/native/attribute-query-in-is-where.test.tsx
× .test:where([data-test='abc']) on data-test=abc matches: true (18 ms)
√ .test:where([data-test='abc']) on data-test=xyz matches: false (4 ms)
× .test:is([data-test='abc'], [data-other='xyz']) on data-test=abc matches: true (1 ms)
√ .test:is([data-test='abc']) on data-test=abc matches: true (1 ms)
● .test:where([data-test='abc']) on data-test=abc matches: true
expect(received).toBe(expected) // Object.is equality
Expected: true
Received: false
11 | registerCSS(`${selector} { width: 37px; }`);
12 | render(<View testID={testID} className="test" dataSet={{ test: value }} />);
> 13 | expect(screen.getByTestId(testID).props.style?.width === 37).toBe(expected);
| ^
14 | });
15 |
at toBe (src/__tests__/native/attribute-query-in-is-where.test.tsx:13:64)
● .test:is([data-test='abc'], [data-other='xyz']) on data-test=abc matches: true
expect(received).toBe(expected) // Object.is equality
Expected: true
Received: false
11 | registerCSS(`${selector} { width: 37px; }`);
12 | render(<View testID={testID} className="test" dataSet={{ test: value }} />);
> 13 | expect(screen.getByTestId(testID).props.style?.width === 37).toBe(expected);
| ^
14 | });
15 |
at toBe (src/__tests__/native/attribute-query-in-is-where.test.tsx:13:64)
Test Suites: 1 failed, 1 total
Tests: 2 failed, 2 passed, 4 total
Snapshots: 0 total
Time: 1.049 s, estimated 2 s
Ran all test suites matching /src\\__tests__\\native\\attribute-query-in-is-where.test.tsx/i.
Reproducible example repository
https://github.com/YevheniiKotyrlo/react-native-css/tree/repro/541-is-where-attribute-queries
- Lingua principale
- TypeScript
- Stelle
- 166
- Fork
- 45
- Merge medio
- 13g 14h
- PR unite (30g)
- 1
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di nativewind/react-native-css
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
nativewind/react-native-css#545 ·
I maintainer di solito rispondono entro 3 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
nativewind/react-native-css#544 ·
I maintainer di solito rispondono entro 3 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
nativewind/react-native-css#543 ·
I maintainer di solito rispondono entro 3 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 84/100
nativewind/react-native-css#540 ·
I maintainer di solito rispondono entro 3 giorni
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
nativewind/react-native-css#538 ·
I maintainer di solito rispondono entro 3 giorni
Tutte le issue di nativewind/react-native-css
Issue simili
-
bug ready-for-agent
Difficoltà 2/5 1-3 ore Idoneità per principianti 73/100
PhyberApex/kuroshiro#1687 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 73/100
microsoft/monaco-editor#5563 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 1 giorno
-
bug
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 86/100
awslabs/visual-asset-management-system#937 ·
I maintainer di solito rispondono entro 1 giorno
-
enhancement
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100