In most policy editors, you can specify fallback policies that MCS will use as replacements if it fails to locate a device variant in a policy referred to in your XDIME code. The exceptions are the script and the rollover image policies.
In most policy editors, you can specify fallback policies that MCS will use as replacements if it fails to locate a device variant in a policy referred to in your XDIME code. The exceptions are the script and the rollover image policies.
You choose fallbacks from policies that you have already defined, either in the policy wizard when you add a new policy, or in the attributes section of the editor. Different policies allow varying numbers and types of fallback. Refer to Policy attributes for details.
MCS handles fallback for different policies in a broadly similar way.
MCS searches first for a suitable variant among those in the fallback policy of the same type
If there is no fallback policy of the same type, and there are image or audio fallbacks, MCS will attempt to find a variant in those policies.
If neither of these are specified MCS outputs the alt attribute on the matching XDIME element
If the alt value is not specified MCS uses the text from any text fallback policy
If no text variant can be found or no fallback text policy is specified, MCS generates no output
If you define a fallback text policy for a link, MCS uses it instead of generating a link without applying any special formatting.
Because script policies do not support fallback, you will need to use the noscript element to provide alternate content in the absence of a script.