I'm not sure if the implementation of such a feature could be done that easily as one would have to implement the whole logic behind CSS. BBEdit is a text editor not a rendering engine (it uses Webkit for it's preview) and such page rendering features might steer the ship into unknown waters (e.g.: how should such a parser handle invalid but common CSS hacks?) So my (outside) guess is, that you shouldn't hold your breath for this to come to BBEdit. Fortunately there are more adequate tools for your problem. In case you don't know it, the Firefox extension Dust-Me Selectors does exactly what you are looking for: http://www.sitepoint.com/dustmeselectors/
Hope this helps Roland Am 04.11.2008 um 15:29 schrieb Arle: > > Just a feature suggestion (not a biggie, but one I run into often > enough it would be handy): > > I regularly deal with XHTML content with moderately complex style > sheets. In the course of things these style sheets tend to get a bit > crufted up with detritus from the development process. It would be > great to have the ability to easily find all styles that are not used > in a given document. It's not quite as simple as it might sound > because of inheritance issues, but shouldn't be too hard. I'm not a > programmer or I'd try to do it myself. > > Just throwing it out as a handy feature to consider. > > Best, > > Arle Lommel > > > --~--~---------~--~----~------------~-------~--~----~ 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. -~----------~----~----~----~------~----~------~--~---
