FireBrick Custom CSS: Difference between revisions

IIt recommendis recommended that you should not attempt to include newlines in the inline CSS of your data URI, as this may be forbidden by the URI scheme standard. 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. See both the RFC for the data URI scheme and also the XML standards. Just some examples of illegal characters are ", %, &, >, newlines and there are probably various others, The simple technique of including literal CSS straight, as below, is only usable if the particular fragment of CSS does not contain any problematic characters, otherwise see the next section for a general method.

Example,: straight, inline CSS. (exerciseExercise caution regarding prohibited characters if adapting). In the following example, any line-breaks maywhich be included for readability. These must be removed and the whole string must be entered as a single line.

Note the presence of the comma after <code>text/css</code>. This is essential in a <code>data</data> URI.

You may use base64-encoded <code>data</code> URIs for safety and complete flexibility as shown in the example below. Using base64-encoding removes any risks and problems with illegal characters completely. Note again the presence of the comma, now after the keyword 'base64<code>data</code>'. This is essential in a data URI, whether base64 is used or not.