in reply to html alteration

You can use the suggestions you've got above to do this. However, if the HTML is under your control, I'd strongly suggest you look at fixing it so that it works consistently between IE and NN. This really shouldn't be that hard (unless you're a masochist and trying to support very old v4 browsers), especially if you get browsers to parse your page in 'Strict' mode by using the appropriate DTD.

Keep It Simple: the more things that have to happen from a browser requesting a page to the server sending it back, the more things that can go wrong. Serving flat HTML files is simple. Having client-side code call a CGI, rewrite an (arbitrary?) file is fiddly, fragile, harder to maintain, consumes more server resources and slower.

If you really can't manage to get consistency using HTML & CSS, see if you can at least handle the inconsistency purely on the client-side using Javascript.

Cheers
ViceRaid

Replies are listed 'Best First'.
Re^2: html alteration
by bradcathey (Prior) on Jul 19, 2004 at 11:48 UTC
    I couldn't agree more. In fact, I'd like to see your HTML to see what you are talking about (maybe outside of the Monastery walls). I spend much of my time getting web pages to work across browsers (especially since moving to all CSS-tableless-XHTML). I'm sure there's a way to solve your problem on the client side (again, provided you aren't trying to do something crazy like make it work in <6.0 NS).

    —Brad
    "Don't ever take a fence down until you know the reason it was put up. " G. K. Chesterton
Re^2: html alteration
by Fletch (Bishop) on Jul 19, 2004 at 13:41 UTC

    Hear, hear. See also Designing With Web Standards (ISBN ISBN 0735712018) for why browser-dependent hacks are evil.