Victor, thanks for the background information.
On Tue, 2 Aug 2005 09:19 am, Victor Mote wrote: > Manuel Mall wrote: > > BTW, why do we have the 3 columns Basic | Extended | Complete? > > Every row will only have one cell out of those 3 filled out. > > Wouldn't it make more sense to have a single column called > > Compliance or Core with the values Basic, Extended or Complete? > > That would save valuable screen space and give us room to add > > columns for each release. > > The original compliance page had each cell color-coded to indicate > compliance with each of the three levels. So, if feature A is > required for "Extended" support and was not supported by FOP, the > "Basic" column would have the "compliant" color, while the "Extended" > and "Complete" columns would have the "non-compliant" color. > ... I managed to revive the color coding (see http://www.arcus.com.au/fop/compliance.html). It was a CSS issue in that the FOP custom stylesheet rules were less specific than the Forrest default CSS rules and therefore not applied on the table elements. Manuel > Victor Mote
