You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
If I use css logical properties (as part of the postcss-preset-env), something like padding-inline is correctly transformed. Though, when I use padding-inline-start, the plugin generates new selectors (e.g. [dir="ltr"] div { padding-left: 1px }) but it is not part of the output.
Logs
n/a
To Reproduce
Use the postcss-preset-env plugin for postcss and use css logical properties that contain start or end in their property.
Describe the bug
If I use css logical properties (as part of the
postcss-preset-env
), something likepadding-inline
is correctly transformed. Though, when I usepadding-inline-start
, the plugin generates new selectors (e.g.[dir="ltr"] div { padding-left: 1px }
) but it is not part of the output.Logs
n/a
To Reproduce
Use the
postcss-preset-env
plugin for postcss and use css logical properties that containstart
orend
in their property.Expected behavior
The output of the postcss logical plugin and postcss dir plugin actually appears in the final css generated by svelte.
Information about your project:
Your browser and the version: https://www.whatsmybrowser.org/b/ZPZGQ
Your operating system: macOS Monterey
svelte-preprocess
version 4.10.7Whether your project uses Webpack or Rollup: Uses vite
The text was updated successfully, but these errors were encountered: