> For the complete documentation index, see [llms.txt](https://docs.didomi.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.didomi.io/consent-management-platform-cmp/consent-notices/restricted-css-expressions.md).

# Restricted CSS expressions

#### What CSS expressions are not allowed in custom CSS?

When configuring custom CSS on your consent notice from the Didomi Console, the following expressions are not allowed:

* *url()*
* *@import()*
* *@charset()*
* *expression()*
* *-moz-binding*
* *javascript*

If one of the listed expressions is used, the Console will prevent you from saving or publishing your consent notice and an error message will be displayed.\
You will not be able to save or publish your consent notice until you remove the expression that is not allowed.

#### Why are CSS expressions not allowed?

We restrict the acceptable CSS expressions in custom CSS for security reasons.

Expressions that load external resources or execute JavaScript can be used to execute code on a webpage. To ensure that the Didomi Console cannot be used for cross-site scripting (XSS), those expressions are blocked.

If you absolutely need those expressions for your custom CSS, you can set them directly on your website and not through the Didomi Console.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.didomi.io/consent-management-platform-cmp/consent-notices/restricted-css-expressions.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.