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
Bookshop components in the editor seem to use the old scoped style system regardless of the package astro version, meaning Astro 3.x components render without their scoped styles in the editor. This doesn't affect builds - just the editor.
Astro 3.0 has recently released, changing how it handles scoped styles. The two main issues are support for the new data-attribute scoped styles, and the change to lowercase scoped style hashes.
Bookshop components in the editor seem to use the old scoped style system regardless of the package astro version, meaning Astro 3.x components render without their scoped styles in the editor. This doesn't affect builds - just the editor.
Examples
Astro 2.x output
Output CSS selector
section:where(.astro-VGEL2S7S)
New default output
scopedStyleStrategy: "attribute"
Output CSS selector
section[data-astro-cid-vgel2s7s]
New output
scopedStyleStrategy: "where"
Output CSS selector
section:where(.astro-vgel2s7s)
New output
scopedStyleStrategy: "class"
Output CSS selector
section.astro-vgel2s7s
CloudCannon Editor output
Same as 2.x; Doesn't match with any of the new CSS selectors
The text was updated successfully, but these errors were encountered: