2019.2

Email clients do not read CSS files and some even remove a <style> tag when it is present in
the email's header. Nevertheless, CSS files can be used with the Email context in the
Designer. When generating output from the Email context, the Designer processes all CSS
rules that apply to the content of the email to inline style properties, as if local formatting was
applied.
1.
From the File types dropdown, select Stylesheets, JavaScripts or all.
2. The list at the left displays the style sheets and/or JavaScript files that are present in the
template's resources. The list at the right shows the style sheets and or JavaScript files
that will be included in the output of the current section (or in all Web sections, if you are
making settings for the Web context). Use the Include and Exclude buttons to move files
from one list to the other.
3. Files are included in the order shown. To change this order, click one of the included files
and use the Up or Down button.
Note
The styles in each following style sheet add up to the styles found in previously
read style sheets. When style sheets have a conflicting rule for the same element,
class or ID, the last style sheet ‘wins’ and overrides the rule found in the previous
style sheet.
JavaScript Properties
The JavaScript Properties dialog appears when you right-click a JavaScript file on the
Resources pane and select Properties. (See also: "Using JavaScript" on page564.)
It contains three options:
l
Name: This option lets you rename the JavaScript resource in the template. The link
between the JavaScript file and Web sections that include it will not be broken by
renaming the file. (See also: "Including a JavaScript file in a Web context" on page567.)
l
Async: When async is checked, the script executes asynchronously with the rest of the
page (while the page continues the parsing).
l
Defer: This option postpones the execution of the script until the page has finished
parsing. This is required by APIs like Google Maps.
Page 944