CSS from Library versus Report Styles

rpolunsky

I finally started migrating my 2.2.1.1 reports to 2.3.0, and I'm seeing a number of issues related to CSS. One of them is the border widths, where 'thin' is no longer a recognized value (the 2.3.0 editor shows "Thin" as the option, so apparently casing is significant).

I've seen comments about the new CSS reference feature in BIRT 2.3 where CSS references from the report's Styles node can include the file at run time for HTML output. I assume that means if you clear the checkbox the file is used for all output formats - is that correct?

My current approach is to reference the CSS file from the RPTLIBRARY file. I define CSS-standard elements in the CSS file, and I define BIRT-only attributes (numeric formats, alternate row coloring) as Style additions in the RPTLIBRARY. That worked in 2.2.1.1 to give me a common presentation across about 24 reports. Do you know of anything in 2.3.0 related to CSS that might give me issues with that approach?