Safari Validator is a Safari extension which allows you to validate your website for (x)html compliance. The actual validation is done by Tidy and the W3C validator. This plugin was initially modeled after a similar plugin for Firefox, which can be found here.
The extension bar will show the amount of warnings and errors the current page has, along with a small icon. Both Tidy and W3C results will be shown, as they may differ sometimes in the amount of errors and warnings.
Clicking on the Tidy results will show the source of the current page. The lines containing errors are highlighted so they can be located easily. Doubleclicking on a warning or error in the list will position the cursor at the correct location in the html source text.
Clicking on the W3C results will open a new browser window, containing the report generated by the W3C validator.
- Latest version for Safari 5: safari-validator-0.3.0.tgz (64-bit Intel only!)
- Unzip the file you downloaded by doubleclicking on it
- Copy Safari Validator.webplugin to ~/Library/Internet Plug-Ins (create the folder if it doesn't exist)
- Double-click Safari Validator.safariextz
- Restart Safari
- Deinstall the Safari extension from the preferences in Safari
- Remove Safari Validator.webplugin from ~/Library/Internet Plug-Ins
- Restart Safari
The software is provided as-is, and I take no responsibility for any unwanted side effects or problems by using it.
If you like the plugin, please consider a small donation.
- HTML5 not (yet) supported
-
10 june 2010 — version 0.3.0
- Rewritten to use the new Safari 5 extension mechanism
- For older versions, see the Safari Tidy plugin.
- Why do my pages load really slowly after installing the plugin?
- The Tidy validation is pretty quick, but the W3C validation is not. Simply disable the W3C validation in the preferences when you're not developing your website.
- Are you using private API's or sneaky tricks to validate the pages?
- No! The combination of the new extension mechanism, along with a webplugin allows for a solution without resorting to private API's. There are still limitations on the extension mechanism (it's just HTML/CSS/Javascript) so a special plugin was made to handle the actual validation.
- What's this <embed> tag doing at the bottom of my documents?
- Don't worry, the embed is just inserted to talk to the plugin. It should not interfere with the rest of the document. If it does, do let me know!