Skip to content

fix(Sass): route the last two direction overrides through ltr-rtl() - #683

Merged
mrholek merged 1 commit into
v6-devfrom
fix/translate-middle-rtl-flag-v6
Aug 4, 2026
Merged

fix(Sass): route the last two direction overrides through ltr-rtl()#683
mrholek merged 1 commit into
v6-devfrom
fix/translate-middle-rtl-flag-v6

Conversation

@mrholek

@mrholek mrholek commented Aug 4, 2026

Copy link
Copy Markdown
Member

Follow-up to #675 and #682, which crossed each other.

Two direction overrides were written as bare [dir="rtl"] rules instead of ltr-rtl() calls, so they ignored $enable-ltr/$enable-rtl:

An LTR-only build ($enable-rtl: false) still shipped them, and an RTL-only build ($enable-ltr: false) could not get the mirrored value as its base, which is the whole point of that mode.

Verified: default build unchanged (both overrides still emitted), $enable-rtl: false now drops them (grep -c 'dir=rtl] .translate-middle' goes 2 → 0, submenu 1 → 0). Sass suite 43/43, class API guard, stylelint.

Both were written as bare [dir="rtl"] rules, so they ignored the flags
that now decide what a build contains: an LTR-only build still carried
them, and the mixin is the only place that knows an RTL-only build wants
the mirrored value as its base. The submenu chevron was already a mixin
call away; the translate-middle override arrived one PR too early to use
it.
@mrholek
mrholek merged commit 3bfa327 into v6-dev Aug 4, 2026
9 checks passed
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