Page 1 of 1
Suport for multiple hazardsymbols in hazardstatement
Posted: Wed Jan 07, 2026 7:43 pm
by ericding
According to the DITA specification, any number of <hazardsymbol> elements is allowed in a <hazardstatement>. If multiple hazardsymbols are present, the Author view in Oxygen shows these symbols on top of each other, in such a way that only the last of the symbols is fully visible. Also, the editor does not show the <hazardsymbol>-tags, even if the view is set to full tags.
It would be nice if:
- the Author view would support multiple <hazardsymbol>-elements per <hazardstatement>, preferably by showing the symbols under each other instead of 'stacked';
- the <hazardsymbol>-tags should follow the visibility settings for tags.
Re: Suport for multiple hazardsymbols in hazardstatement
Posted: Thu Jan 08, 2026 8:44 am
by Radu
Hello,
Thanks for reporting this problem, we have an internal issue for it and I added your feedback to the opened issue. Pasting the issue ID for future reference:
EXM-55737 Two hazardsymbol elements are displayed in the same visual space
The CSS style which is to blame for this is defined in "OXYGEN_INSTALL_DIR/frameworks/dita/css/core/-domain-hazard-d.css" and it looks something like this:
Code: Select all
*[class~="hazard-d/hazardsymbol"] {
display:block !important;
position:absolute;
bottom:0.3in;
left:0.1in;
max-width:1in;
max-height:1in;
-oxy-display-tags:none;
}
It causes multiple hazard symbols to be displayed in the same space and also changes the tags display to none.
The current CSS selector makes sense if there is only one hazard symbol because it displays the <hazardstatement> as a table like structure with the hazard symbol aligned to the left of the message panel.
A possible workaround when there are two hazardsymbols would be to create a custom CSS for DITA XML editing
Code: Select all
*[class~="hazard-d/hazardsymbol"]{
bottom:inherit;
top:1in;
}
*[class~="hazard-d/hazardsymbol"] + *[class~="hazard-d/hazardsymbol"]{
top:2.2in;
}
and set it up in a DITA framework extension customization:
https://blog.oxygenxml.com/topics/customizeDITACSS.html
Regards,
Radu