Yohanes Santoso wrote: > On second thought, since I'm using vm, then perhaps the solution is as > simple as intercepting vm before it writes to HttpResponse. >
Use an external filtering servlet and modify Jetspeed to forward all output to this servlet... > I think programatically optimising HTML is a hairy thing to do. Are > there are other alternatives to solve the 'nested table' problem? > The "nested tables" are required for the portal operation in HTML because it's the only portable way to guarantee portlet output independance. To work around the NS4.77 issue (and not switching to Mozilla or Opera) you can possibly try to remove the 2 first nested tables and use layers+js positioning instead. However, this will probably means that you'll need to have a portal layout version for NS2.77 and another for all the other HTML browsers... It's very unbfortunate that NS4.77 has such a fucked implementation of table rendering but I don't see any non specific alternative since its CSS-P support is completely screwed up... -- Raphael Luta - [EMAIL PROTECTED] Professional Services Manager Vivendi Universal Networks - Paris -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
