www.remarpro.com – W3C Validation results

Was there a question in there? Or are you just voicing an opinion?

Hi,

Yes, indirectly I am looking for some solutions.

When we use css3 “border-radius” , W3C indicates “Parse Error Empty String” error. I dont find any solution to this issue. So I checked big websites like www.remarpro.com, cssmania.org, they have the same issue when validating their sites.

It is a prestigious issue for these big websites, so they might find a solution, or otherwise they might intimate this issue to W3C, because this is new , even most websites might not know this issues associated with their websites, becoz W3C changes their mind without intimating the community and without any reasons.

Giants like wordpress’s words are audible to W3C. I am pretty sure there is no reason for this error “Parse Error Empty String” for using border-radius.

So I am making you all to have an awareness about this and you might check your websites and there might be some solutions or at least W3C should realize their mistakes.

Riaz

When we use css3 “border-radius” , W3C indicates “Parse Error Empty String” error. I dont find any solution to this issue.

First – check that you’re validating against the correct CSS level. Secondly, you have to bear in mind that there is a big difference between having perfectly valid CSS and have CSS that passes the validator. The latter is just a tool, requires bug fixes every now & then and is not perfect. It’s intended to be used as a tool – not as a definitive statement on whether your CSS is valid or not. You have to check the errors that it thinks exist and determine, for yourself, whether these are real errors or not.

General rule of thumb: Don’t switch your brain off when you press the validate button.

becoz W3C changes their mind without intimating the community and without any reasons.

Not true. You can contact W3C whenever you like. You can become involved in various ways if you want. You can mail bug reports to the developers of the various validators. I’ve done all three.

If you have an issue with the validator or think you have found a bug, use the bug report link on the page to contact W3C.

Hi,

1. Yes, I have checked with the correct level (css3) but no use.

2. I checked the bug report area , but there is a big queue with issues already submitted but there is no response from them for months. So i dont want to waste my time.

My conclusion:

Many internet users are thinking that W3C is a big authority validating the code and this should not be exist anymore because it is bad for developers like us when our clients are dissatisfied with the results while validating thier websites in W3C. They are not good enough to validate our sites with their dustbin scripts.

WordPress has a voice to make awareness about this to stop their big mistakes ,I hope.

Many internet users are thinking that W3C is a big authority

It is. It is the international authority that defines all web standards. Without it, there would probably be something resembling chaos. The validator tools are provided as a free service to help developers comply with those standards but given all of the other work that W3C does (and it is huge), the tools are going to be low on their list of priorities.

If you don’t like the validators, don’t use them. Validate your markup & CSS manually against the appropriate W3C specification document. The specification documents are the final word on the subject, after all.

Hi,

Ok, finally whats your suggestion , whats your opinion about this issue ” Parse error empty string” , do you know any solution for it ? are you able to find right now? if you are not able to find then what would be your suggestion on W3C validator ?

Just advising me not to using that W3C is not a solution at all, but on behalf of wordpress or as a good theme developer you should say whether W3C is a perfect validator or not, you should say the truth in a straight forward way, and should let others to know that. Will you?

This is like Internet Explorer, We the theme development community all hate using IE, but for cross-browser compatibility , we are forced to consider several things to make IE compatible. Like that we dont want to validate our code, but W3C validator has become a trend now a days , we need to prove that they are not working properly now, we hope our voices will correct them or otherwise they should come up with a reason for this “parse error”.

Regards
Riaz

Just advising me not to using that W3C is not a solution at all,

I did not advise you to stop using the W3C validator. I said that you have to use it as a tool and interpret it’s results accordingly. If in doubt, cross-check against the appropriate W3C CSS specification document.

Will you?

I’ve already said that it is only a parsing tool and as such, is subject to bugs. If in doubt, cross-check against the appropriate W3C CSS specification document.

Hi,

Ok , thanks, but it is not an expected solution, any how thanks for your time and support.