Bug CSS warnings: Chris Pederick's Web Developer 1.1.9

Did I say this: "As you say, it all depends on what is the main purpose for which you have created your site." ??
I'm not here for a debate or to discuss philosophy just want to know if someone knows and can explain to me in detail a way of fixing these warnings.
To answer your question re kunena .org does it reflect similar/same warnings the answer is yes.
So my question is regarding CSS warnings in the latest version of kunena, does anyone know?
Thanks in advance.

I paraphrased. No, you did not use those exact words. Yes, the tool does throw those same warnings on K.org (we've been discussing this topic behind the scenes and my colleagues can confirm these things).

The question is "Does this technical issue require a solution?" That's something each web developer must answer for him/herself. Should these technical problems be matters to be worried about? Again, that's a question each web developer must answer for themselves.

Work is ongoing to continually improve Kunena so that, in future versions, these kinds of things will not occur (or not occur to the extent that people will see evidence of them today). The matters you have brought to our attention will be dealt with, more constructively, as we go forward and develop K 2.0. Will they be dealt with in K 1.7.2? Almost certainly, because K 1.7 is now at end-of-life, the answer is no.

Can users have confidence that we and they have done everything humanly possible to remedy these kinds of issues? That's a bit like the "how long is a piece of string" question. We're doing what we can with the resources that we have at our disposal.

Is this a problem that requires an urgent solution? Again, that's something we can talk about. I would be interested to hear what others may have to say and would like to contribute to this topic.

Can they be fixed? In all probability, these things can be fixed. But, while anything is possible, everything has a cost. So, really, perhaps the question might better be asked "Should these problems be fixed?" ... and that is something that I cannot answer with certainty.

fair enough, it's a great!! component and very much appreciated,I'll wait for the next version. the social networking integration looks excellent and just what I need for a new site I'm slowly working on.
I do realise what you are saying and agree with it, it's a lot of work creating a program like Kunena more than I can comprehend

many thanks
Steve

I know this is a few weeks old, but I thought I would mention one thing. As I was looking at the CSS errors that are happening with FF I got to checking a few out. If you were to do a search for lets say "css filter" you would find that this is a IE specific CSS property. So in short you could correct these simply if you did not want cross browser compliant by just removing them. Or by finding a better way to style the CSS for those errors so that it will be compliant with both FF and IE at the same time. What FF is doing is that it sees these IE specific CSS properties and just drops them due to that they are either not supported or not needed.

Hope that helps a little bit for ya.

Jake