- 1 Internal Enhancements Requests
- 2 Files needed
- 3 delete tidy_last_validated.html on exit
- 4 CSS VALITATION
Internal Enhancements Requests
PLEASE DO NOT EDIT
Disable frame validation
I don't know if I already asked, but I would like to see the ability to make tidy not check inline frames (or force validation to the current URL domain). I'm thinking about adsense which are never valid, and make show the ugly error or warning emblem :)
WA The domain filter can be used to WA this.
- Go in options
- Choose validate in all domain except : googlesyndication.com
I'm requesting that if there is a validation error, that the statusbar icon flash once every second or so. I imagine some people would prefer that there would be options like
. flash rate . continuous or first x seconds
Thanks for such a great tool!
Possibly not a good UI practice. It is too disturbing.
HTML / XSLT and generated source validation
I just took a look at your HTML Validator plugin for Firefox (Version 0.836), and wanted to thank you for creating such a useful tool. I've also got an enhancement request or two, which would make it much more useful for the things I'm working on.
Thanks again for making this tool!
Very good idea and it should be not too difficult to do.
<?xml version="1.0" encoding="iso-8859-1"?>
<xsl:output method="xml" version="1.0" encoding="ISO-8859-1" omit-xml-declaration="no" standalone="yes" doctype-public="-//W3C//DTD XHTML 1.1//EN" doctype-system="http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd" cdata-section-elements="script style" indent="yes" media-type="text/xml" />
<xsl:template match="/"> <html> <head><title>XSLT Test</title></head> <body>
Current Price: <xsl:value-of select="catalog/cd/price"/>
</body> </html> </xsl:template> </xsl:stylesheet>
<?xml version="1.0" encoding="iso-8859-1"?> <?xml-stylesheet type="text/xsl" href="HelloWorld.xsl"?> <catalog>
<cd> <title>Empire Burlesque</title> <artist>Bob Dylan</artist> <country>USA</country> <company>Columbia</company> <price>10.90</price> <year>1985</year> </cd>
DTD used in the Tooltip
First, thank you for the excellent and helpful extension. I appreciate your work very much.
Second, I have a small suggestion (or request) for the extension. When the icon appears indicating the page is valid or contains warnings or errors, it would be helpful to know what DOCTYPE the extension is validating against without having the view the code. I'm wondering if that information could be added to the screen tip that appears when hovering over the icon. For example, under "HTML Validation Result," maybe it could read "XHTML 1.0 Strict" if that's the DOCTYPE. This bit of information would be a timesaver when navigating quickly through a site just to make sure everything checks out.
Again, thanks for your efforts on the extension and for your willingness to consider my idea.
Best regards, Michael S.
Integration with Selenium
Can your great tool be used with Selenium to test the validity of dynamically generated HTML?
Open View Source in same window
Love your extension.
Was not able to register for forum - username kept getting rejected.
Anyway, my suggestion is to have an option to have the source validator always open in the same window. I use the validator a lot, and I always forget to close the window, so after a while I have a whole bunch of source windows open. It's a pain to go through closing them all.
Popup Window when not 0/0
First thanks for the best firefox plugin ever!
While developing http://crowdnews.eu I have noticed that I sometimes overlooked some errors and warnings.
I would therefor like to suggest that it become possible to mark domains for popup warnings.
delete tidy_last_validated.html on exit
tidy_last_validated.html contains a copy of the last page visited, even after FF exits.
I don't think this is right - Firefox has privacy settings to remove cached data precisely in order to avoid this sort of thing being left behind.
I think the add-on should remove this file (perhaps wipe it first by over-writing with 0 bytes) as soon as it is no longer needed. When FF exits at the latest. Maybe it only needs to do this if the user has the relevant privacy settings enabled, but it might be easier to do it always than to work out what combinations of settings should provoke it.
Obviously there are other ways to prevent the file being a problem: file access permissions, whole-disk encryption, or just don't share your computer with others. But since FF provides the delete-on-exit function, I think it would be best for add-ons to do so too.