I'm not sure it really would need to implement so much. It would need to be able to see inheritance within CSS (e.g., it would need to know that "body .content h3" would mean that body and .content are used, not just h3) but that's not terribly difficult. Then it could match a list of style elements, ID names and style classes against the values from the document to see what ones aren't used at all. For example, if you have "body .content h3" in your CSS and it finds that there are no instances of <h3> in the context of something with the style "content" it would tell you that that isn't used. There's nothing about rendering here, just rather about knowing what selectors match what.
The bit about common hacks is more problematic, but I'd even be content with just valid use of CSS since what I develop I validate against the W3C tools. I wasn't aware of Dust-Me. I'll have to look into it. Unfortunately the CMS I use for sites (Typo3) does not work with Firefox 3.x (it did with 2.x), so it would mean keeping yet another browser open... -Arle --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "BBEdit Talk" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/bbedit?hl=en If you have a specific feature request or would like to report a suspected (or confirmed) problem with the software, please email to "[EMAIL PROTECTED]" rather than posting to the group. -~----------~----~----~----~------~----~------~--~---
