CSS and other errors from the manager?

OT IE Browser Comment:

First: IE7 is here now and it isn’t horrible.

Second: MS intends to deliver it to all Windows Update Automatic Updates subscribers as a Security Patch on XP (legit copies only).

Third: Too many corporate sites develop for IE and either use a boatload of junk code that cracks like an eggshell or antiquated browser sniffers that block users from even using their site. While this is the company’s fault, eliminating IE from a user’s PC can be a pain becuase it limits access, and in the end user’s mind, means that the browser is broken not the site. (My father-in-law [in the group of fastest growing internet users in North America, 50+] is a prime example. He was a user of NS4.7 up until last year but most sites, using even the slightest amount of linked CSS, would bring his PC to a screeching halt. I upgraded him to Fx but I left IE on there because there were a number of sites that break horribly in Fx that he visits regularly. I installed the IE Switch Extension in Fx and now he can do what he wants and, when he encounters a site that won’t work in Fx he just switches browsers)

Fourth: You cannot eliminate support for the browser with the largest market share unless maybe if you are building sites exclusively to be visited by web developers. It is not good dev practice much like not supporting FF or using crappy browser sniffers.

Back on topic:
Since the thread topic’s OP relates to design and invalid CSS in the manager, I wouldn’t care that much until we see a 1.+ version. The function, security, and front end presentation are of first importance. If a library has some legacy proprietary CSS and the rest of the library is necessary to keep MODx working as expected don’t drop it for the sake of back end CSS validation. This is, in my opinion a finishing touch and not a key issue or bug.