This topic addresses some common problems encountered when formatting reports with cascading style sheets (CSS).

What problems did you encounter? If you have troubleshooting suggestions that you think others will find helpful, you may send them to be considered for inclusion in a future release. You can:

• E-mail them to books_info@ibi.com. Please include your name and phone number, and put Cascading Style Sheet troubleshooting for FOCUS applications in the subject line.
• Send them to:

  Documentation Services

  Attn: Core Reporting Group
  Information Builders
  Two Penn Plaza
  New York, NY 10121-2898

  Please include your name, phone number, e-mail address, and postal address.

Symptom: The report is not using any of the cascading style sheet's formatting.

• Reason 1: Your Web browser may not support cascading style sheets.

  Solution 1: Check to be sure that your browser supports cascading style sheets; if it does not, install an appropriate browser version.

• Reason 2: Your Web browser may be set to ignore cascading style sheets.

  Solution 2: Reset the browser to accept a document's cascading style sheet. For instructions about checking or changing a browser's setting, see your browser's help.

Symptom: The report reflects some, but not all, of the CSS formatting.

• Reason 1: The support and implementation of cascading style sheets in your web browser determines how a cascading style sheet rule formats your report. It has nothing to do with FOCUS. You may experience this symptom because your browser does not support the level of cascading style sheets that you are using, leaving some CSS features unimplemented.

  Solution 1: Upgrade your browser to a version that supports all the CSS features used to format the report, or edit the cascading style sheet to remove features that are unsupported by some of the browsers that are used to display the report.

• Reason 2: Your web browser may be set to use your personal cascading style sheet, and you may have rules there that override those specified in the cascading style sheet assigned to the report. See your third-party CSS documentation.

  Solution 2: Reset your browser to accept the cascading style sheet for each document, or edit the rules in the two cascading style sheets so that they no longer conflict.

• Reason 3: Certain web browsers ignore an entire rule if they do not support a property specified in it. If your web browser does not support a property specified in a rule for one of the classes assigned to the report, none of the report components to which that rule was assigned are formatted.

  Solution 3: Remove the unsupported property, or upgrade your browser to a version that supports the property.

• Reason 4: Each report component can be assigned only one cascading style sheet class. If you have specified more than one class, only the first one specified is assigned to the component; the others are ignored.

  If a class has not yet been assigned to a report cell, and you specify conditional formatting for it, only the first class whose condition is satisfied by that row is assigned to the cell. The others are ignored.

  Solution 4: Do not assign more than one CSS class to each report component. If you need to apply multiple attributes, bundle them into a single class.

• Reason 5: Some web browsers implement CSS inheritance rules for nested elements in ways that do not conform to the CSS standard. If you are using such a browser, for example, you specify some formatting in a rule for the BODY element, your browser may not apply the rule to other elements nested within BODY.

  Solution 5: Specify the formatting of a report in a rule for a different element (for example, if the browser does not correctly implement inheritance from BODY, use a rule for TD), or else upgrade your browser to a version that correctly supports inheritance.

• Reason 6: External cascading style sheets can be subject to certain restrictions when used with other formatting methods. For example, if the FOCUS StyleSheet for a report does not generate an internal cascading style sheet, but it references external CSS classes and also specifies native FOCUS StyleSheet attributes, there may be a formatting conflict.

  Solution 6: The solution depends on the kind of formatting conflict. In the example above, the solution is to generate an internal cascading style sheet.