Andrew,
Although I'm not Shaun I thought I would respond with my personal opinion on your most recent post. These are just my opinions, and are nothing more than that.
Andrew Hawes wrote
I appreciate your time, but could you respond to my original post. Aren't you personally embarrassed by the fact that the forums have this glaring CSS issue in FireFox? Isn't this the type of thing that can make a good product look stupid even while it is functionally no big deal?
I agree that the CSS issue is an annoyance, but many sites have "quirks" in different browsers. In fact my local TV stations, and schools have CSS quirks that affect certain browsers. Yes it is an issue, yes it needs to be resolved, but it does NOT impact functionality. I personally would say that the forums e-mail notifications, and other issues are WELL past the CSS issue in priority, AND visibility. A community forum site that doesn't update individuals on the content that they wished to be updated on, is not a community site that people will want to return to, thus in my opinion a much bigger, visible, black eye.
Andrew Hawes wrote
BTW: The built-in spell check doesn't work and FireFox's spell check won't work in here either. These are things I just take for granted on most sites.
The errors with the editor are a third party providers issue. The TextEditor control utilizes the FCK editor, that editor has its own set of known issues that impact its functionality. Personally aside from trying to find ANOTHER third party solution for the editor, this one is a bit hard to resolve. I personally am about to resolve it on my sites by using the RadEditor from Telerik, but that is NOT an option for widespread DotNetNuke distribution due to licensing requirements.
I guess my point is yes, there are issues, but really in the grand scheme of things, there are bigger fish to fry than an CSS error, and other items. Prioritization is the key to getting the issues resolved in the proper order.