From Htmlpedia
Revision as of 07:13, 18 May 2011 by Mgueury (talk | contribs)
(diff) ←Older revision | Current revision (diff) | Newer revision→ (diff)
Jump to: navigation, search


Internal Bugs


############## Version 0.795 ##############

Vista and normal end-users


It seems there is a problem to install Html Validator as a normal user on Vista. But it seems to work with another type of user that has more privilege


I have no Vista and never seen the problem. I think this is due to the fact

  • that Vista does not allow Normal users to install binary on their machine.
  • but the extension has to be installed by the user who want to use it
  • but seen the extension contains a binary, it does not work

I do not know if I can do something about this.


Hi Colin, I think it is due to a C++ librayr called nstidy.dll that you can find in the profile directory of Firefox. I have no Vista and never seen the problem. I think this is due to the fact

  • that Vista does not allow Normal users to install binary on their machine.
  • but the extension need to be installed like the user who use it
  • but seems the extension contains a binary, it does not work

Kyle, that I CC here, asked if copying this DLL in the Fire fox directory would work. I think so !! If you copy the file" nstidy.dll " + a empty file called ".autoreg" to Program File/Mozilla Firefox, it should make the extension work as a normal user.

Normally they resides in a directory like just after the installation of the extension. C:\Documents and Settings\<User>\Application Data\Mozilla\Firefox\Profiles\xxx User\extensions\{3b56bcc7-54e5-44a2-9b44-66c3ef58c13e}\components

You can also download the extension (.xpi) file. Rename it to .zip, unzip the file to find the files you would need.

But without Vista, I can not help more. I am interested if you succeed to let it work to add this to the FAQ.



Response Here's what happened...I copied those two file into the directory and nothing i added myself to the users in the security panel as Full Control for the Mozilla Firefox folder, then I uninstalled FF, then reinstalled it and it worked! I don't know what I did to make it work. but now it's working! the Addon's says .8.3.4. So it's the right one. It's telling me right now that Yahoo mail beta has 70 errors! Thanks for all the suggestions. Now I can do my web design homework.


Add to this the FAQ. Log possibly a Firefox bug on Vista.

Linux and Firefox


It seems that on some Linux system since, the extension make Firefox to

  • or crash at startup
  • or when it validates a page like


I tried with a Firefox downloaded from and the extension downloaded from (0.75) and it was working. I used SuSE SLES 9.0.

############## Version 0.8x ##############

Linux directory permission =


Problem to use 0.8x on Linux.


Icon is always green and "0 error / 0 warnings" shown.


Got this mail: I have found the problem. Directory "tidy" in my Firefox profile was without "x": /home/vitaly/.mozilla/firefox/yf32cs6a.default# ls -la |grep tidy drw-r--r-- 2 vitaly wheel 48 2006-09-11 14:12 tidy I changed permissions and now all works fine. Can you set permissions during extension installation?


Update the FAQ. Try to check the bundling ?

Tidy and the button tag


############## website ##############

Table should be replaced by CSS


See Gerard page :) !

############## User Interface ##############

Text edit problem


It seems that some users have problem to edit some text when the extension is enabled at the same time than Firebug.


It seems that

  • loosing the focus on the application but going to another program
  • then come back to firefox work-around the problem.

Testcase =

  • Install Firefox 2.0. HTML Validator <0.836 and Firebug 1.0
  • Home page must be blank
  • Go to google
  • Type something
  • CTRL+ arrow does not work


Idem in 0.796 ? Log a bug in bugzilla


Reported on MAcOSX 0.795 and Windows with Firefox 2.0.0.x


Added the tooltip in an onmouseover in place of directly. New function: addTooltip : function()

XP and end-users

The extension appears as (v) -/- when runned on XP as an end-users


Added an error message in TidyInstall.js. The good solution would be not to store files in the c:\program files\mozilla firefox

But how ? since there is a problem when user name has special char in his name...

Icon and frames, sometimes, the main page is green

When I am working on my page locally, the icon suddenly stops showing a problem but shows a green check anyway. The summary then shows some exclaimation marks for the various frames, but nothing for "nn errors/nn warnings" so there is just a dash. It does work when I bring up the frame's source in the source viewer though.

Testcase =

None but I have already seen it.

Cleanup XHTML / uppercase

like the uppercase-options in the page cleanup should be grayed out when you selected XHTML

DOCTYPE and XML stylesheet

> I appear to have come across a strange bug with the plugin regarding the > OpenSP section of the validator. > > As you are aware with proper XHTML you can include CSS with an XML > stylesheet declaration refer to both: < > > and < > > your validator seems to cope fine > with a generic: > > <?xml-stylesheet href="common.css" type="text/css"?> > > However, it flags tonnes of errors if the 'media attribute' is added, > for example: > > <?xml-stylesheet href="common.css" type="text/css" > media="screen,projection"?> > > Apparently it seems to then flag "false errors" for some reason when the > media attribute is added.


This is a bug of the extension. I was unaware of it. What happens is that the extension looks for the DOCTYPE in the first 100 characters, and due that all the stylesheet are before, he does not find it and default to HTML. Then generates all the errors you see because your page is a XHTML one. I will add this in the bugs to solve.

It is not a question of media but of length of the string before the doctype.

Thanks for reporting the problem,


XHTML, AJAX validation and <.../>

Example of this bug:


Problem: This page validates as correct XHTML 1.0 Transitional when it is loaded, but after the ajax call is run all of the "br" tags change from this "
" to this "
" even though All of the code in the example pages is valid xhtml. The problem is not limited to "br" tags. All single-element-tags seem to do this (input for example).

I don't know if this is a firefox problem or a plugin problem but i thought i'd point it out. I would really love to have a plugin that could validate post-ajax xhtml code right in the browser.


Validation only of file://

I really like the extension. I am using version and would like to update to the current version since I believe the one I have is a beta. But I like to use the following list of domains to validate:,, localhost. This works fine in but although I can add the others just fine to the Allow list in the new version, I cannot get localhost (pages still on my computer and not yet uploaded) to be added to the Allow list. I saw a post saying to right-click the icon to allow it, but the only option for local pages seems to be a general Enable for everything. Firefox on Win XP if it mattters. Thanks


To fix

Block and frames choice

I need to exclude all domains serving ads. When a page contains frames/iframes double-clicking on the status icon/text brings up a dialog asking to "Select the page or one of its frames/iframes" for "View Source". I think it should be possible to add domains from that dialog directly to the block list. Also, the menu on the (enhanced) "View Source" page should have a quick way to add to the block list.

Installation on Linux and Seamonkey

Trying to install 0.839 for Linux on Seamonkey I get an "install script not found" message. XPI for Linux doesn't contain the install.js. Would be nice if this could be corrected.

Problem with extension when installed globally


W3c validator 0.8

[ANN] Markup Validator 0.8.0 released from olivier Thereaux on 2007-07-25 ( from July 2007)

Does this release impact to the current version of your extension? I mean, does the extension show the same parsing result with Markup Validator 0.8.0 at this moment?

DTD with missing /

This "-//W3C/DTD XHTML 1.0 Strict//EN" works in the w3c validator and not in the extension.

It should be ?? "-//W3C//DTD XHTML 1.0 Strict//EN"

Leak in Firefox

> Hi Marc. > > I have discovered a memory leak in your plug-in (tidy). I have set the the tidy.options.debug flag to true, but no error log was created.. Probably because tidy didn't crash. I don't know if you use system variables but on my system (Windows XP Pro Danish version) the suggested folders doesn't exist ( c:\program files\mozilla firefox\tidy). I have pasted the content from Leak Monitor below. > > Regards, Jon. > > To reproduce: > > 1. Double click on error icon on a page with HTML errors. > 2. Hit F5 to reload page. > 3. Close the window. > > > From Leak Monitor: > Leaks in window 0x53e5cb0: > [+] [leaked object] (53eca50) = [Object] > [ ] timeout = 0 > [+] notifySelectionChanged (53eca48, chrome://global/content/viewSource.js, 23-26) = [Function] > [ ] prototype (1299ff0) = [Object]

Hi Marc. Leak Monitor is a Firefox plug-in: Jack Slocum has written a small article about what you should be careful with, when manipulation the DOM:

If you have Leak Monitor installed you should be able to reproduce the leak by:

  1. Double click on error icon on a page with HTML errors.
  2. Hit F5 to reload page.
  3. Close the window.

Cheers, Jon!

   Hi Jon,
   I normally do not do any memory cleanup in Javascript since normally it garbage collect for me.
   I do not know the leak monitor ? How does it work ? Where do you see this info ?
   Ps: the diagnostics logging is now in your "firefox profile directory"/tidy/

Hang in

Google look for BEAS -> open 2 -> + 1 news -> close tab HANG only in Firefox 2 (it works in Firefox 3)

Tried to test several WA and could not find a good one...

WebDeveloper / Shortcut


There seems to be a new conflict between Tidy html validator and the web developer extensions.

the default keyboard shortcut for "edit css" in web dev is ctr/cmd+shift+E. the html validator seems to overwrite this with a copy something(can't remember what - I've disabled it for the moment) to clipboard function that is not configurable.

Disabling the tidy extension (in the add-ons window) seems to fix the problem.

minimac 1.5 core solo (lame I know, only free mac in office) Firefox 3.0.1 Mac os-x 10.5.4 html validator web-dev 1.1.6 firebug 1.2.0b7, firecookie 0.6, y-slow 0.9.5b2 firegestures 1.1.2 show-ip 0.8 colorzilla 2.0

startup code and validation

OS: Linux i686 Firefox: 3.0.1, Debian release HTML Validator:

I have noticed that HTML Validator in tidy mode seems to ignore tidy.options.filter when the browser is first started, because the status bar icon shows the yellow warning icon instead of the blue ok icon on pages where the blue icon should be displayed. It is fixed by opening the view source window, and possibly by opening the HTML Validator options menu or other HTML Validator menus.

It turns out tidy.options.filter is correctly parsed by buildFilterArray() (tidyUtil.js:394) when the browser is started. However, initTranslation() on the tidy object (nsTidy.cpp:901) clears the 'disabled' property for all messages. tidyUtil's translation() function (tidyUtil.js:663) calls initTranslation() but will only call buildFilterArray() if tidy.options.debug is on or the defaultLanguage is not en-US. So if debug is off and the language is en-US, the result is that tidy.options.filter has no effect.

I can think of two possible solutions offhand:

1. Have translation() call buildFilterArray() unconditionally.
2. Do not have initTranslation() clear the 'disabled' property.

I don't know which is better, and there may be other options. I have confirmed that the first option (see attached) does fix the bug.


--- content/tidyUtil.js 2008-06-10 17:50:16.000000000 -0400 +++ content/tidyUtil.js 2008-07-29 09:30:49.000000000 -0400 @@ -704,8 +704,6 @@

          this.tidy.setTranslationPrefix( prefix, linecol );

- - this.buildFilterArray();

        // Translate the description of the extension. 
        var tidydesc = Components.classes[";1"].getService(Components.interfaces.nsIPrefService).getBranch("extensions.{3b56bcc7-54e5-44a2-9b44-66c3ef58c13e}.");

@@ -717,6 +715,9 @@

        oTidyUtil.tidy.log( '<ERROR>translation exception, defaultLanguage= ' + this.defaultLanguage );

+ + // Reload filter list + this.buildFilterArray();


Error and

<?xml version="1.0" encoding="utf-8"?><!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Strict//EN" "">
 <p><a href="blabla" onclick="somefunction('<img src=\'blabla\'/>')">asfdsadf</a></p>

This HTML does not give any error in HTML Validator but well in the real one... I do not know why...

Character set mismatch

Hi Marc,

Congratulations on a truly excellent Firefox extension. I have a suggestion : the W3C parser checks that the charset set in meta tag matches the charset in the HTTP header. If not the same then a warning is shown. I noticed this as this was the only validation error your extension did not detect for my site. I had the following in my HTML code: <meta http-equiv="Content-Type" content="text/html; charset=utf-8"> My web server HTTP response header was: Content-Type: text/html; charset=iso-8859-1 The W3C warning was:

     Character Encoding mismatch!
     The character encoding specified in the HTTP header (iso-8859-1) is different from the value in the <meta> element (utf-8). I will use the value from the HTTP header (iso-8859-1) for this validation.

Thanks again for an excellent extension, I hope this is useful to you.


Difference with the validator of W3c

Hi there Marc.

I just wanted to report what appears to be a bug with version of the HTML validator for Firefox 3.0.4. When I validate this page:

I get the following warnings:

Result: 0 errors / 3 warnings

line 48 column 75 - Warning: inserting implicit <label> line 48 column 75 - Warning: replacing unexpected button by </button> line 48 column 7 - Warning: missing </button> Info: Doctype given is "-//W3C//DTD XHTML 1.0 Transitional//EN" Info: Document content looks like XHTML 1.0 Transitional

... but taking a look at the source code, the warnings seem completely unfounded.

Thanks very much for this great tool by the way. I have been using it for several years now to ensure the quality of my html and xhtml source and I always recommend it to others.

Je viens de remarquer que vous avez une adresse email Vous parlez français peut-etre? J'ai habité a Mons en Belgique pendant trois ans et je l'adore. J'ai encore quelques amis là-bas.



-> Seems to be a bug in TIDY

Hanging and mails

I want to thank you for this wonderful plugin, it saves me hours of time with my website when I make HTML changes or adjustments.

For many months I encountered a problem retrieving my telephone voice mail, Optimum Online with the Firefox browser: Infinite loop when retrieving the page, then firefox would not close event using File Exit or Exit Firefox extension. Unfortunately the page needs my userid and password so it's not directly accessable by anyone else unless I divulge my credentials. I contacted Optimum Online who said they think it's a Firefox install issue. After testing on other userids where it works, I started a debugging procedure of my Firefox profile and setup:

  1. The page works with IE7 and my Guest user version of Firefox. I suspect my profile or plugins.
  2. Found I was a level down on the HTML Validator and installed BTW there was no notice from Firefox that an update was available.
  3. Disabled Dom Inspector and HTML Validator. The page works.
  4. Re-enable Dom Inspector The page works
  5. Unchecked the "Enable validation in browser" flag. The page failed.
  6. I reset the "Enable validation" flag to checked;enabled Tidy debugging; restarted the browser; and recreated the problem.
  7. Firefox looped and would not end as before. I killed it using the Vista Task Manager as before.
  8. Copied the tidy debugging files to a non-volitile area; turned of Tidy debugging and the "Enable Validation"; restarted Firefox
  9. The copied files are attached

My system Dell E1505, 2 gig memory, Vista Sp1 Home Premium with all updates; Firefox 3.0.4, Avast Anti Virus, No software firewall other than Windows Firewall (Yes I know Inbound only but I'm careful and behind a hardware firewall)

Firefox extensions

   * Dom Inspector
   * Exit button Firefox
   * Gmail space
   * Hide Unvisited
   * HTML Validator
   * IE View
   * Neo Diggler
   * ShowIP
   * Window Resizer
   * WML Browser (disabled)

Should you have any questions of me or need me to test anything for you please let me know.

-> see C:\my_prog\mozilla\src\bug\2008_12_19_hangings_log for logs

Tidy new option

Hi Marc

I have just found a related Tidy option:

The merge-divs argument was added in Tidy version 1.70

It was added in response to this bug report:

It would be useful to myself if "Cleanup the page" made this argument optional or set it to "no" by default.

Regards, -Andrew


Hi Jens,

There is a long time I have not seen something similar. What happens probably is that my extension called the function to get the cache of Mozilla and this functions probably hangs after such event. I will check.

Thanks for the bug report,


> Hello, > > there is a bug in your extension which force pages which use XMLHttpRequests to hang if you change the page before the XHR request was finished. > > Here you'll find an example page to reproduce the problem, here: > > > Switch in the top menu to "Advanced Search" and before the page got completely loaded, back to the "Search" page. > You will see that the browser shows the loading icon and hangs (just the page loading hangs, not the complete browser). > > This only happens if your extension is enabled, if I disable it everything works fine. > I've tested that on different computers using Firefox 3.5.2 and 3.5.3 in Windows XP and Windows Vista, using version of your extension - and it is reproduceable on all computers. > > This happened also on other pages, but this is the first time where I figured out, that your extension must be the source of the problem - because everything works fine if I disable it. > > If you have further questions, feel free to email me. > > Many regards, > Jens

List of Frames

Hi Marc,

I was testing an HTML page today that had a frameset containing 100 frames, and I noticed a couple of minor bugs in the dialog that pops up to ask you which frame you want to view the source from.

1. Only the lines in the list that are visible have an icon at the start of the line. Those that you have to scroll down to see do not. 2. If you resize this dialog the list stays the same size and does not stretch.


W3c error and HTML Validator not


Take a look at this example page I set up:

The W3 validate show and error, but this plugin says the page is valid. Can you fix this bug? Also, the plugin always shows an "X" in the status bar for SSL-secured sites. Is this a bug or expected behavior?




Using the HTML 5 Doctype, HTML Tidy is flagging an error for it.

HTML Doctype: <!DOCTYPE html>

Error reported: line 1 column 14 - Error: no internal or external document type declaration subset; will parse without validation

Hidden icon

Hi Marc,

I've just found another related minor issue.

If you have a warning in a document in a frame and have previously hidden that warning, the status icon of the parent document still shows the yellow exclamation mark rather than the blue tick, and the dialog that lists the frames that contains warnings doesn't mention the warning being hidden.


Thanks for updating the HTML validator add-on to work with Firefox 3.6. It’s really handy to see at a glance if a page is invalid, and I’ve been using it for years. However, I’m sure the Mozilla folks would really appreciate it if you updated the Firefox logo it uses to the current version, which can be found here:


Firefox 2.0

This web page says it supports Firefox 2: I am using Firefox and used it in the past on another Windows XP machine. Ben Millard: UI Developer

Syntax error not in

Thanks for HTML Validator. Its really a big support for every QA. Actually we found an error in the parser:

checking this on w3c it says ok with the Validator there is an eror: <a href="#"><button type="button" class="clickBtn">Click here!</button></a>

Problem not found


Just wanted to report a minor miss in the HTML Validator Firefox add-on.

In one of my href strings I inadvertently had the sub-string:
&amp& [note missing semicolon after first 'p']
instead of plain

The W3C Validator caught this; your otherwise-wonderful HTML Validator did not.

Thought you'd like to know. Thank you for your first-rate add-on.

error in tidyutils.js

I am using your HTML Validator in firefox 3.6.6 and I like it very much. Congratulations for this amazing add on!
On some sites the browser shows no reaction anymore and there is a script failure:
Skript: chrome://tidy/content/tidyUtil.js:1214
This error occurs e.g. on when I am logged into my account. But as I need your add on for my own site only I would like to know if there is a way to block it on any other site than mine? I can only block single domains/subdomains but not e.g. every page except mine. Is there any way?
Thanks in advance.
Kind regards

different result than W3c

Hi Marc,

I've just started using your fine plugin for Firefox and, although I find it useful, it gives me different results than I get online from the W3C validator.

I believe that in my case the document type is not detected correctly.  I'll tell you why below.
I've checked, which starts with the following header:
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "">
Yet, when I click on one of the attribute errors, I find this line:
·         Incorrect choice of the document type. Deprecated attributes are not part of HTML 4.01 Strict.

Note the use of "HTML 4.01 Strict", which is clearly not correct. 
I use Wordpress and I have a feeling many people will benefit from your investigation of this issue.

Thank you,


I have installed the latest version of HTML validator into Firefox, but 
am unable to access its preferences dialog because of the yellow screen 
of death, caused (presumably) by an incomplete Lithuanian localization 
of HTML Validator.

As a Mozilla localizer, I suggest that you should either drop incomplete 
localizations when packaging HTML Validator releases, or (preferably) 
merge missing strings from the en-US locale. Mozilla has a tool which 
does that and is already being used in the process of building nightlies 
of Firefox and other apps. You can read more about it at, and maybe some 
other locations (this is pretty much the first link that Google gave 
me). I think you should employ this or similar tool when producing HTML 
Validator releases, because otherwise your users are left with 
incomplete functionality (e.g. it seems I cannot validate any pages now, 
and not even sure why as I can't access the extension's preferences).

I hope you'll find this e-mail helpful. I'm also cc'ing Edgaras, the 
author of Lithuanian localization of your extension – maybe he'll want 
to update it... :)

Addon all-in-one-sidebar

I have been looking for the "evildoers" and have found him. The AddOn All-In-One Sidebar is responsible. Unfortunately, I think in the Einstein Ellingen of AddOns not an option for the source code.

Could you try to find a solution?

Thank you