My first reply to someone elses post
My understanding is that the html rendering engine (gecko) used by kmeleon is maintained at mozilla.org. kmeleon is everything but the html rendering. Netscape6 uses gecko also - but webdevelopers tend to go as far as to only check and fix their pages for Netscape6, which will be a different (older and bugger) version of gecko.
The best place to post about bugs in rendering of pages is with the bugzilla tracking part of mozilla.org. Its a big site and it would require a bit of effort and to narrow down what was going wrong to be helpful to the folks there and make sure that the problem had not been already reported or fixed. When posting to bugzilla people should really people should check that the problem is still there with the nightly mozilla source code - ie that someone didnt fix the bug yesterday. That really involves compiling it yourself which is a bit hardcore - especially as new bug slip into the daily builds.
If there is a site that you use alot such as your webmail site that really fails in kmeleon I suggest trying either:
* mail the webmaster and smile sweetly and ask if they could check there site against kmeleon. I am trying to convince a site or two by offering the support team goodies from thinkgeek.com (no joy yet!).
* get the latest code from mozilla and compile your kmeleon against it to see if the problem was bug that slipped in between the version of gecko that n6 and km05.
In the log run gecko will settle down and netscape6 and other members of the gecko family will render all pages the same. Website will then naturally tidy themselves up to work with the family of folks in the free world. Just by using kmeleon you are doing your part for all the family. Your on the winning team as kmeleons redering will continue to benifit from the improvements make to gecko by all the opensourcers.