CSP Provider
Configures CSP-related behavior for inline tags rendered by Sveltery Base components.
Anatomy
Import the component and wrap it around your app:
Some Sveltery Base components render inline <style> or <script> tags for functionality such as removing scrollbars or pre-hydration behavior. Under a strict Content Security Policy (CSP), these tags may be blocked unless they include a matching nonce attribute.
CSPProvider allows configuring this behavior globally for all Sveltery Base components within its tree.
Supplying a nonce
If you enforce a CSP that blocks inline tags by default, configure your server to:
- Generate a random nonce per request
- Include it in your CSP header (via
style-src-elem/script-src) - Pass the same nonce into
CSPProviderduring rendering
In SvelteKit, generate the nonce and set the header in hooks.server.ts:
Then return the nonce from a layout load function and pass it to the provider:
This will ensure that all inline <style> and <script> tags rendered by Sveltery Base components include the correct nonce attribute, allowing them to function under your CSP.
Disable inline style elements
You can avoid supplying a nonce if you disable inline <style> elements entirely and rely on external stylesheets only. The relevant components are <ScrollArea.Root> and <Select.Popup>. They inject a style tag that disables native scrollbars on <ScrollArea.Viewport>, and on <Select.Popup> or <Select.List> when alignItemWithTrigger is enabled.
Specify disableStyleElements to remove these tags:
<script> tags across all components are opt-in, so they are not affected by this prop and don't have their own disable flag. A nonce is required if any component uses inline scripts.
Inline style attributes
CSPProvider covers inline <style> and <script> tags rendered as elements, but it does not cover inline style attributes (for example, <div style="...">). The style-src-attr directive in CSP governs inline style attributes encountered when parsing HTML from server-rendered components (it does not affect client-side JavaScript that sets styles).
In CSP, style-src applies to both <style> elements and style="" attributes. If you only want to control <style> elements, use style-src-elem instead.
If your CSP blocks inline style attributes in addition to elements, you have a few options:
- Relax your CSP by adding
'unsafe-inline'to thestyle-src-attrdirective (or using onlystyle-src-eleminstead ofstyle-src). Style attributes specifically pose a less severe security risk than style elements, but this approach may not be acceptable in high-security environments. - Render the affected components only on the client, so that no inline styles are present in the initial HTML.
- Manually unset inline styles and specify them in your CSS instead. A part's
styleprop is merged into its own inline styles, so it cannot remove them. Use the part'srendersnippet and dropstylefrom the props it receives. Note that you'll need to ensure you vet upgrades for any new inline styles added by Sveltery Base components.
API reference
CSPProvider
nonce string | undefined —
- Name
- Description
The nonce value to apply to inline
<style>and<script>tags.- Type
string | undefined
disableStyleElements boolean | undefined false
- Name
- Description
Whether inline
<style>elements created by Base UI components should not be rendered. Instead, components must specify the CSS styles via custom class names or other methods.- Type
boolean | undefined- Default
false