style-conflict
The style-conflict element declares behavior to be used
when one or more flagging methods collide on a single content element.
In case of conflicts between flagging methods at different levels (for example, a section is flagged green and a paragraph within the section is flagged red), the most deeply nested flagging method applies.
In case of conflicts between flagging methods on the same element (for example, a single element is being flagged with both green and red color), it is recommended that the conflicts be resolved as follows:
| Flagging method | Conflict behavior |
|---|---|
| startflag/endflag | Add all flags that apply. |
| color | Follow the style-conflict @foreground-conflict-color setting, or use an output-appropriate default color if no conflict color is set. |
| backcolor | Follow the style-conflict @background-conflict-color setting, or use an output-appropriate default color if no conflict color is set. |
| style | Add all font styles that apply. If two different kinds of underline are used, default to the heaviest (double underline) and use the foreground-conflict-color. |
| changebar | Add all change bars that apply. |
Contains
(empty)
Contained by
Example
See the example in the <val> description.
Attributes
| Name | Description | Data Type | Default Value | Required? |
|---|---|---|---|---|
| foreground-conflict-color |
mp: question prompted by jeff ogden: should
we document the @ convention for identifying attributes in the front
part of the spec?
TC response: yes The
color to be used when more than one flagging color applies to a single
content element.
|
CDATA | #IMPLIED | no |
| background-conflict-color | The color to be used when more than one flagging background color applies to a single content element. | CDATA | #IMPLIED | no |