Re: [Htmlvalidator-help] html tidy 0.7.9 crashes FF 1.5.0.4
Brought to you by:
mgueury
From: Marc G. <mg...@sk...> - 2006-06-07 23:15:30
|
Hi Andy, the last validation page you gave is the faq of my site. It is probably=20 not the page crashing the browser. Please give also give me the following info: - which OS do you use (Linux32 bits 64bits Windows ??) - which processor (AMD 64 ??) - Please give me a step by step that would allow me to reproduce the issu= e. - Do you use accessibility checking, which level ? - Does it happens always, or only with a specific page - If so be sure to send me the specific page. It is probably a bug in=20 Tidy. Thanks by advance, Marc CCing to the mailing list And...@wi... wrote: > Here are the logs: > > > > This is due to embedded html inside of <pre> tags - the original web pa= ge=20 > is a 'blosxom' generated page, from diffs of my code updates. Some of = the=20 > code changed includes perl that is print html something like: > --- > =20 >> PrintString("</TD>\n"); >> ########################################### >> # Option for which county # >> ########################################### >> >> PrintString("<TD valign=3Dtop align=3Dright>County</TD>= <TD=20 >> =20 > valign=3Dtop>"); > =20 >> SelectCode('county','County','3','Y','co_code','co_translation'); >> PrintString("</TD><TR>\n"); >> =20 > > > > command line tidy warns about the "<TD>" tags found: > line 193 column 1 - Warning: missing </pre> before <td> > line 203 column 51 - Warning: missing </b> before </td> > > Changing those in the source to "<TD>" keeps FF from crashing.=20 > > Hope this is enough info.=20 > > Thanks,=20 > > a > > Andy Bach, Sys. Mangler > Internet: and...@wi...=20 > VOICE: (608) 261-5738 FAX 264-5932 > > "Strange women lying in ponds distributing swords is no basis for a sys= tem > of government. Supreme executive power derives from a mandate from the > masses, not from some farcical aquatic ceremony." > -- Dennis - Monty Python and the Holy Grail > > -----------------------------------------------------------------------= - > > > =09 > > > Problems / FAQ > > > First, the extension is at his beginning. And not complete at all=20 > <todo.html> :-) > I do my best, but I know that it is not perfect. > > If you have a problem not listed here, please do not hesitate to=20 > contact me: mg...@sk... <mailto:mg...@sk...> > If you have the possibility, please give me the logs of the diagnostic=20 > logging <#DIAGLOG>. > > > 1. The numbers of errors in the view source is different than > the one seen in the browser (Firefox 1.0 only) > > There is a big bug in Firefox 1.0 and corrected in 1.5. The HTML=20 > source seen in the view source is sometimes 'modified' by Firefox. And=20 > the source seen is for most page a little different than the one sent=20 > by the webserver. > https://bugzilla.mozilla.org/show_bug.cgi?id=3D57724 > > There is a side effect on the extension in Firefox 1.0 > > * In the browser, it works. At the icon of the status bar, the > HTML sent by the webserver is validated > * But in the view source, the HTML is a little different and > sometimes contains more or less errors than the real page=20 > > This looks like a small problem. But it is annoying when trying to=20 > remove all the errors. > > Solution: The real solution is to use Firefox 1.5 if possible. > Work-around: Right click on the icon in the browser and choose "copy=20 > errors to clipboard" > > > 2. The extension does not work. > > Check that you installed the extension for your Operating system. The=20 > extension is available for Windows, Linux, and MacOSX > > > 3. The extension does not work on Linux ( ex: Fedora Core 4, > Mandriva 2006 ) > > Symptoms: The icon in the browser is always green and the text is -/-.=20 > Or an error windows appears after installing the extension in version=20 > 0.77 and after. > > Cause: When installing the extension, you are using a C library that I=20 > compiled with a older LIBC++ version than the one distributed with=20 > Fedora Core 4. Unhapilly both are incompatible. Another symptom is=20 > that if you download the real Firefox compiled in the same way from=20 > the Mozilla.org website, it gives this error. > > error while loading shared libraries: libstdc++.so.5: cannot open=20 > shared object file: No such file or directory > > On Fedora Core 4: > Solution: you need to install I compat-libstdc++ (yum install=20 > compat-libstdc++-33) > > On Mandriva 2006: > Solution: > - stop Firefox > - install libstdc++5 by typing "urpmi libstdc++5" in a console, as=20 > root or by using the Mandriva Control Center and the package installer. > - reinstall the extension > > On Ubuntu 5.10: > Solution: > sudo apt-get install libstdc++5 =20 > > On Slackware xxx > Solution: install cxxlibs-5.1.0-i486-1 > > On Cent OS 4 > > > yum install compat-libstdc++-33 > > yum install mozilla-nspr > > On another type of linux with the problem, > you can try this to know which .so are missing to run the extension=20 > correctly. > > cd ~/.mozilla/firefox/<xxxxxxxx>/extensions/{3b56bcc7-54e5-44a2-9b44-= 66c3ef58c13e}/components > > ldd libnstidy.so > linux-gate.so.1 =3D> (0xffffe000) > libplds4.so =3D> not found > libplc4.so =3D> not found > libnspr4.so =3D> not found > libpthread.so.0 =3D> /lib/tls/libpthread.so.0 (0x40067000) > libdl.so.2 =3D> /lib/libdl.so.2 (0x40078000) > libstdc++.so.5 =3D> /usr/lib/libstdc++.so.5 (0x4007b000) > libm.so.6 =3D> /lib/tls/libm.so.6 (0x40138000) > libgcc_s.so.1 =3D> /lib/libgcc_s.so.1 (0x4015a000) > libc.so.6 =3D> /lib/tls/libc.so.6 (0x40162000) > /lib/ld-linux.so.2 =3D> /lib/ld-linux.so.2 (0x80000000) > > =20 > This is the output you should see. It is normal that the 3 libs above=20 > are not found as they are part of Firefox. The other libraries are=20 > normally part of the Linux ditribution. If they are misssing, it means=20 > that the extension will probably not work. Most of the time, you will=20 > need to install the LIBC compatibility package from your linux=20 > distribution to make all .so resolve correctly. > > If you find such a type of Linux, and find a solution for your=20 > installation, please send me a mail and I will write down the solution=20 > like I did for Fedora Core 4, Mandriva 2006 above. Thanks by advance. > > > 4. The Firefox 1.0 version does not work with Firefox 1.5 or > Mozilla 1.8 trunk=20 > > An error appears on the screen when starting Firefox > > XPCOM:EventReceiver > The procedure entry point ?Clone@nsMemory@@SAPAXBXI@Z could not be=20 > found in the dynamic library xpcom.dll > > Firefox 1.1 and Mozilla 1.8 have rewritten the XPCOM library. I have=20 > no control on this at all. A side effect of that change is the error=20 > message above. What happens is that the extension uses the function=20 > nsMemory::Clone. But the function is not anymore in XPCOM.dll of=20 > Firefox 1.1. The only solution was to make a separate version with a=20 > new tidy DLL compatible with 1.1. > > You can find it in the download <download.html> area. > - reinstall the extension for Firefox 1.5 > - and restart the browser. > > Solution: This is solved in version 0.62 > > > 5. It is not available for my platform (Solaris, Hp UX, Aix,...= .) > > The extension contains a part in C/C++ with the validation logic. It=20 > needs to be recompiled on each platform. > Ideally, there should be an extension .xpi, by platform. But it is=20 > unrealistic. I would need to maintain it for each version of Mozilla=20 > or Firefox for each platform. > There is currently a Windows, Linux and MacOsX version in the Download=20 > <download.html> area. > > The code <download.html> is normally compilable for each platforms. I=20 > will try to solve this, like this: > > * the compilation instructions <compile.html> are available here. > * or the ideal is to have the C part in Mozilla cvs, or Firefox. > So it would be compiled automatically by the mozilla build > machines. But I dream there. > > > 6. No line numbers > > * In the version 0.8x of the extension, there will be a line > numbering. See here. <preview_080.html> > * Mozilla 1.7, 1.8 has a status bar indicating the line and column > number. > You can WA the problem by doing: Edit / Go to Line... (CTRL+L) > I suppose that future Firefox versions based on a later mozilla > version will have this feature. > > > 7. All the warnings/errors are not documented > > Please wait for a next version > See : to do <todo.html> > > > 8. I can not hide the validation in the page source. The page > source validate also non HTML content (css, javascript, ...) > > Open the options and check [x] Disable validation in the View Source > > > 9. Sometimes after the installation the extension does not work. > > * You need to close the browser and restart it to see it working. > Sometimes, you need to uninstall the extension. Then install agai= n. > > * For Mozilla at least, you need to be admistrator on Windows to > be able to install the extension. > > * You are using the TabBrowser Extensions > <http://piro.sakura.ne.jp/xul/_tabextensions.html.en> (TBE) > TBE can depending of his settings change the window containing > the View Source. For example, if you have choosen to see the > source in a tab, the Validator can not be used. You can correct > this by resetting the default value of TBE. > 1) Go in Tools/Extensions > 2) Choose TBE and click Options > 3) Go in Use Tab / View Source > 4) Ask to see the source in normal mode > 5) Restart the Browser. > > > 10. Some menu options are disabled in the page source menus. > > Some menu items are disabled in the menu. It is Firefox behavior. I=20 > have no idea neither, why these menu are there if they can not be used. > Mozilla 1.7, 1.8 has not such problems. > > > 11. The HTML in the page source is not the one of my page. > > It appears in very rare case that the HTML source is not the one given=20 > by the server. > This is due to a mozilla bug.=20 > https://bugzilla.mozilla.org/show_bug.cgi?id=3D57724 > > Solution: This bug is solved in version Firefox 1.5 and (1.0+) > > > 12. How to remove all the extensions in a normal Mozilla > installation when for example the profile is corrupted. > > > Step 1 - Find the Mozilla profile directory > > For ex: > Windows : C:\Documents and Settings\your_user_name\Application=20 > Data\Mozilla\profiles\default\xxxxxxx.slt\ > Unix : ~/.mozilla > > Check in the profile directory that it is the good one. > Open the file the Profiles\default\XXXXXXX.slt\bookmarks.html > And verify that it is well your latest bookmarks list. > > > Step 2 - Backup > > Take a backup of all the prrofiles =3D the Profiles directory (for ex:=20 > zip it) -> profiles.zip > It is always a good idea to make a backup regularly of these profiles=20 > and keep it on another hardware in case of unexpected problems. > > > Step 3 - Remove overlays > > Go to the subdirectory chrome in your profile > C:\Documents and Settings\your_user_name\Application=20 > Data\Mozilla\Profiles\default\xxxxxxx.slt\chrome > > Check that Mozilla is stopped > Rename directory overlayinfo in overlayinfo.old > > Restart Mozilla and all extensions should be gone. > > > 13. The validation errors are not the same than the W3C validat= or > > W3c has made 2 programs to verify the HTML syntax. Both uses different=20 > algorithms: > - W3C Validator <http://validator.w3.org> is based on SGML and the=20 > verification of the DTD of the page (defined in the DOCTYPE) > - HTML Tidy <http://tidy.sourceforge.net/> is called a 'linter',=20 > lexer. In short, it parses the page and try to understand the errors. > > Both technologies have their advantages and disadvantages. This=20 > extension is based on HTML Tidy <http://tidy.sourceforge.net/>, it=20 > includes the code of Tidy without changes. From my experience, the=20 > errors are the same in the 2 programs except that Tidy shows more=20 > errors. It shows errors about attributes values. And it tries also to=20 > clean the page of useless, empty tags and so on. > > Tidy has an accessibility-checker included. Also, it can clean up a=20 > HTML page. It is interesting to help people to find solutions for=20 > their errors. > > If you have questions about the validation result, there is a user=20 > list and with archives :http://lists.w3.org/Archives/Public/html-tidy/ > > > 14. The validation text is in Czech > > Symptoms: > - You see for example for 0 chyb/0 varov=E1n=ED in the icon text. > - You have installed the extension 0.72 to 0.74 with Firefox working=20 > in non-translated version of the extension (ex Portuguese) > - Even, if the fix is in version 0.75, unhappily, installing 0.75 will=20 > not solve the issue ! > > The problem is that the chrome.rdf file of the profile is now=20 > corrupted and can not be corrected by a new version of the extension.=20 > Let's correct it manually. > > Solution: > - Before installing the version 0.75 or higher. Go to your=20 > profile/chrome directory > Windows: c:\document and settings\<user>\application=20 > data\Mozilla\firefox\Profile\<id>\Chrome > Unix: ~/mozilla/firefox/<id>/chrome > a. one solution is to remove the file chrome.rdf but you will loose=20 > all your extension. > b. the other solution is to edit the chrome.rdf and to correct it by=20 > switching the czech and english line. > Look for the line containing : resource=3D"urn:mozilla:locale:cs-C= Z" > > Wrong > ... > <RDF:Seq RDF:about=3D"urn:mozilla:locale:root"> > <RDF:li RDF:resource=3D"urn:mozilla:locale:cs-CZ"/> > ... > <RDF:li RDF:resource=3D"urn:mozilla:locale:en-US"/> > ... > > Right (en-US should be at the top) > ... > <RDF:Seq RDF:about=3D"urn:mozilla:locale:root"> > <RDF:li RDF:resource=3D"urn:mozilla:locale:en-US"/> > ... > <RDF:li RDF:resource=3D"urn:mozilla:locale:cz-CZ"/> > > > 15. Installation of the extension is blocked > > Whatever you do, the extension is never installed and is blocked by=20 > firefox. You see a blcoked green line on the top of the browser. > > Solution: > If you disabled xpinstall in Firefox 1.0.x by unselecting the "Allow=20 > Web sites to Install Software" preference, you will not be able to=20 > install HTML Validator on Firefox 1.5. Go to about:config and set the=20 > xpinstall.enabled preference to true to re-enable installs. > > > 16. The extension crashes or hangs and you would like to > report a problem/bug not listed above. > > Please be sure to use the version 0.59 or later. In these versions,=20 > there is a diagnostic logging that can be created for helping me to=20 > determine the cause to the issue. To enable it: > 1. Start Firefox./Mozilla > 2. In the URL line, type: about:config > In the filter box type : tidy > 3. Edit the properties "tidy.options.diaglog_dir". It is empty,=20 > disabled, by default. > Type in the value the directory where the extension will write the=20 > logs files. > ex: c:\temp to store the log file in the c:\temp directory on windo= ws > /tmp for Unix > 4. Set also the propery "tidy.options.debug" to true > 5. Stop Firefox / Start Firefox. > 6. Reproduce the issue. > 7. Send me (mg...@sk... <mailto:mg...@sk...>) the 2 logs=20 > files: tidy_firefox_diag.log, tidy_last_validated.html > with a description on how to reproduce the issue. > > Thanks by advance. > |