Firefox HTML VALIDATOR (based on Tidy and OpenSP)

[Dr.CSS]

found this, it works in line in the status bar no going to third party web site, rite clik for hilited error code, it found 4 errors on this form page, heres one...


line 121 column 6 - Warning: unexpected or duplicate quote mark

EDIT: sorry forgot the link...
http://users.skynet.be/mgueury/mozilla/

[parisja]

Nice find!

I'm sure this will come in handy, thanks.

[Piratos]

This Validator does not work correct.

Best solution is the original w3 validator local installation.

http://forum.cmsmadesimple.org/index.ph ... 386.0.html

[mahjong]

This Validator does not work correct.

I'm using it all the time. Never had a problem.

Why are saying it "does not work correct" ?

[Dr.CSS]

Piratos

You are correct, the more I use it the more I notice that it will give false errors on some very obvious things.

this is giving three errors.


Spring 2006


line 56 column 3 - Warning: missing before
line 57 column 5 - Warning: inserting implicit
line 58 column 1 - Warning: discarding unexpected

I think it is expecting them to be inline with each other.

Spring 2006

[mahjong]

I think it is expecting them to be inline with each other.

Spring 2006

No, not at all. Tidy is suggesting this would make more sense:
...
Sprint 2006


By the way, both of you seemed to be unaware that Firefox's HTML Validator is also offered with the same SGML engine as W3C Validator.

[Dr.CSS]

Spring is supposed to be an h3 and bold, this is not considered an error by the w3c validater, I've run it thru without getting an error for this.

[mahjong]

The only way Spring could be bold while an header is if your tags are nested this way : Sprint 2006

[Piratos]

Testing as Example a domain of the show off:


http://www.wareriver.com  Firefox AddOn 10 Warnings

W3 Validator 11 Errors

Below are the results of checking this document for XML well-formedness and validity.

  1. Error Line 24 column 47: document type does not allow element "a" here; assuming missing "object" start-tag .

      onclick="window.open(this.href);return(false);">

      ✉
  2. Error Line 34 column 17: an attribute value specification must be an attribute value literal unless SHORTTAG YES is specified .

     

      The mentioned element is not allowed to appear in the context in which you've placed it; the other mentioned elements are the only ones that are both allowed there and can contain the element mentioned. This might mean that you need a containing element, or possibly that you've forgotten to close a previous element.

      One possible cause for this message is that you have attempted to put a block-level element (such as "" or "") inside an inline element (such as "", "", or "").

      ✉
  4. Error Line 43 column 97: document type does not allow element "link" here .

      ...r.com/stylesheet.php?templateid=11" />

      The element named above was found in a context where it is not allowed. This could mean that you have incorrectly nested elements -- such as a "style" element in the "body" section instead of inside "head" -- or two elements that overlap (which is not allowed).

      One common cause for this error is the use of XHTML syntax in HTML documents. Due to HTML's rules of implicitly closed elements, this error can create cascading effects. For instance, using XHTML's "self-closing" tags for "meta" and "link" in the "head" section of a HTML document may cause the parser to infer the end of the "head" section and the beginning of the "body" section (where "link" and "meta" are not allowed; hence the reported error).

      ✉
  5. Error Line 46 column 101: document type does not allow element "link" here .

      .../wareriver.com/index.php?page=home" />

      ✉
  6. Error Line 48 column 83: document type does not allow element "link" here .

      ...areriver.com/index.php?page=Resume" />

      ✉
  7. Error Line 52 column 228: document type does not allow element "link" here .

      ...01number=20&cntnt01returnid=15" />

      ✉
  8. Error Line 52 column 235: end tag for "object" omitted, but OMITTAG NO was specified .

      ...r=20&cntnt01returnid=15" />

      You may have neglected to close an element, or perhaps you meant to "self-close" an element, that is, ending it with "/>" instead of ">".

      ✉
  9. Info Line 23 column 0: start tag was here .

     

      The value of an attribute contained something that is not allowed by the specified syntax for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; the variant “selected=""” is not allowed.

      ✉
  11. Error Line 201 column 150: value of attribute "align" cannot be ""; must be one of "left", "center", "right" .

      ...1" cellpadding="1" border="0" align="" summary="">

      The value of the attribute is defined to be one of a list of possible values but in the document it contained something that is not allowed for that type of attribute. For instance, the “selected” attribute must be either minimized as “selected” or spelled out in full as “selected="selected"”; a value like “selected="true"” is not allowed.

[Dr.CSS]

Have you noticed the disclaimer about the W3C Validator.

He is having a problem with that site, the menu doesn't work in IE, any ideas...

[mahjong]

Testing as Example a domain of the show off: http://www.wareriver.com 

Firefox's Validator 0.831 (OpenSP) find exactly the same 10 errors + 1 info as W3C :

[Dr.CSS]

It looks like the beta works better.

[nils73]

I think it is expecting them to be inline with each other.

Spring 2006

Nope ... not at all. You can not wrap a block-level element (h3) inside an inline-element (strong). This is why tidy suggests closing the strong-tag before h3 and opening and closing it afterwards to make it valid. So code would be:


Spring 2006


Which of course would make no sense but tidy could then remove the empty tags ... but the warning of wrapping h3 inside strong is absolutely correct. And about making the h3 look bold: Why not use CSS for that? Separate content from design! If you have already specified h3 with a not-bold-style, then you might want to assign a class to the h3 and make it bold using CSS. Or if you would like to go with your h3-strong-solution:

Spring 2006

Tadaa ... no more validation errors. At least not in this example. I must admit that there are certain cases where Firefox-Tidy does not "validate" properly, but then it is no validator at all. Use it - that is all I can say. And maybe you should activate the help within to get to know what Tidy is about to tell you. It is all about learning proper HTML ... sorry to say.

Regards,
Nils

[Piratos]

Here the picture of my test:



[attachment deleted by admin]

[Piratos]

i have the original w3 validator installed on local webserver with linux and windows and i use it with my daily work.

The firefox extension does never seen the same errors as the w3 validator, often it see only warnings and no errors.

With 0.83.1 - so the Developer, the Extension should deliver the same output as the w3 validator , but that is not true.

I have no advabtage with such a tool and the local installation of the original w3 validator ist the best way and it works.