FireBrick Custom CSS: Difference between revisions

You may use base64-encoded data: URIs for safety and complete flexibility, as you will otherwise have to be aware of the risk of your inline CSS containing characters that are either prohibited in data URIs, illegal in quoted strings or in XML attributes. Just some examples are ", %, &, >, newlines and probably various others, but base64-encoding removes this problem completely. IfNote youthe arepresence usingof anythe non-ASCIIcomma charactersafter inthe your CSS, you should use Unicode text and first UTF-8-encode your text into a byte stream, before thenkeyword base64-encoding those bytes. YouThis ''must''is then also declare that your original CSS text was UTF-8 asessential in thea exampledata below. In the following exampleURI, aeven line-breakif hasbase64 been added for readability. This must be removed and the whole string entered as ais singlenot lineused.