This issue can manifest for a number of different reasons, but the most likely culprit is that the tagged content (fact data) is relying on inheriting style information from a parent block. When that parent block is not part of the tagged content, the style information is inherited properly in the full Inline XBRL document but is not inherited when the tagged content is displayed alone as a fact.
Depending on the structure of your filing and where the tagged content is located in the document, you can try various solutions to correct this problem.
Move the inline XBRL tagging to the parent block
This option is not always possible but it is the simplest solution. If the entire parent block can be included as fact data, simply move your XDX tagging to that parent block before generating your Inline XBRL document. This will ensure that all the style information is included in the fact data when the tagged content is removed from the document to be viewed alone in an XBRL viewer.
However, if moving the tagging to the parent block would include additional information in the tagged content that is not part of the fact data, you will not be able to use this solution. Try some of the other options below.
Use styles that do not rely on the parent block
If you are using style properties that rely on a parent block to determine the value of the property or that rely on other forms of inheritance, those styles will not look the same when they are displayed without the parent block. You can change the styles you are using to remove this kind of dependence on the parent block. For example, use absolute font sizes instead of relative font sizes (e.g., 10pt instead of 90% or .9em).
Move the style onto the tagged content
If possible, you can move the style onto the tagged content by adding an inline FONT tag around the tagged content. Duplicating the style information will not generally affect the appearance of the tagged content in the full Inline XBRL document. (Note, however, that using properties like font sizes that are relative to the parent will cause problems in this case.)
Explicitly set style information that is normally not set
The SEC's Inline XBRL and XBRL Viewers both will add some styling information to your document. These styles may be causing the issues so you can attempt to compensate for these idiosyncrasies by using style properties to reset the styling to a browser's default. For example, instead of using:
style="font: 10pt Arial, Helvetica, Sans-Serif"try
style="font: normal 10pt Arial, Helvetica, Sans-Serif"You can also attempt to use different elements within the tagged content. As as example, the XBRL Viewer may have its own styling used for <H1> tags but have no styling for <P> tags. By avoiding the use of the <H1> tag, you will not have to work around any default styling that may be applied to that tag by the Viewer.
