Pewarta Proxy

📋 Server Request & Proxy Logs

Loading active proxy settings...
Developed by Khairul Adha (adhexa.id)
Mengambil log server...

⚙️ Pengaturan Proxy Target

Skip to content

feat(core): range syntax and rem/em lengths in media queries - #11530

Open
triniwiz wants to merge 2 commits into
mainfrom
feat/css-media-range-syntax
Open

triniwiz wants to merge 2 commits into
mainfrom
feat/css-media-range-syntax

Conversation

@triniwiz

@triniwiz triniwiz commented Oct 15, 2026 •

Copy link
Copy Markdown
Member

PR Checklist

What is the current behavior?

  • Media queries only accept the min-/max- prefix syntax. Tailwind v4 and Bootstrap 6 write every breakpoint in the Media Queries Level 4 range syntax (@media (width >= 40rem)), which fails to parse, so none of their responsive variants (sm:, md:, .col-md-6) ever apply.
  • rem and em in a media query are read as plain numbers: (min-width: 48rem) is 48.

What is the new behavior?

  • Range features are parsed: (width >= 600px), (600px < width), (400px <= width < 700px) and (700px > width >= 400px), combined with media types, and, not and lists as before. Malformed ranges still throw.
  • rem and em are the initial font size, 16, as in CSS. Tailwind's md breakpoint (width >= 48rem) is 768.
  • Other lengths keep their NativeScript meaning: px is a device pixel, and a number without a unit is a device-independent pixel. (In CSS a media query px is a CSS pixel; changing that would change which queries existing apps match, so it is left for a separate discussion.)

Tests: css-mediaquery/index.spec.ts (6) and a stylesheet-level case in css-selector.spec.ts.

Verified with all of these core PRs merged together (#11527–#11537): apps/automated passes on the iOS 26.4 simulator (1830 OK, 0 failed) and on an Android API 36 emulator (1692 OK; the one failure is the network-dependent IMAGE-CACHE.test_ImageCache_ValidUrl timeout, which also passes on reruns).

Media queries now accept the Media Queries Level 4 range syntax:
`(width >= 600px)`, `(600px < width)` and `(400px <= width < 700px)`.
Tailwind v4 and Bootstrap 6 write every breakpoint this way, so
until now none of their responsive variants applied: the query failed
to parse and never matched.

`rem` and `em` in a media query are the initial font size, 16, as in
CSS, so Tailwind's `(width >= 48rem)` is 768. They were read as plain
numbers before (48).

Lengths otherwise keep their meaning: `px` is a device pixel and a
number without a unit is a device-independent pixel.
@nx-cloud

nx-cloud Bot commented Oct 15, 2026 •

Copy link
Copy Markdown

View your CI Pipeline Execution ↗ for commit ead0267

Command Status Duration Result
nx run-many -t build -p core,webpack5,vite ✅ Succeeded 22s View ↗

💡 Verify your cache is correct by running tasks in a sandbox. Read docs ↗


☁️ Nx Cloud last updated this comment at 2026-10-15 20:31:54 UTC

@pkg-pr-new

pkg-pr-new Bot commented Oct 15, 2026 •

Copy link
Copy Markdown

Open in StackBlitz

npm i https://pkg.pr.new/@nativescript/core@11530
npm i https://pkg.pr.new/@nativescript/vite@11530
npm i https://pkg.pr.new/@nativescript/webpack@11530

commit: ead0267

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant