[Plugin] cssRemoveUnusedSelectors

[hobnail]

Originally Posted by DNSB

But @mcdummy did not want the undefined classes removed. He wanted to be informed about them so he could add the required classes. For that, I thought the Report tool was an already implemented solution.

Nevertheless it would still be useful if the plugin removed them from the CSS files. As an option.

Along those lines I've had times when a book has a lot of "crud" html and it would have been nice if Sigil's Report thing would list all of the used html tags.

[hobnail]

Originally Posted by DNSB

But @mcdummy did not want the undefined classes removed. He wanted to be informed about them so he could add the required classes. For that, I thought the Report tool was an already implemented solution.

Nevertheless it would still be useful if the plugin removed undefined CSS as well as unused CSS. As an option.

Along those lines I've had times when a book has a lot of "crud" html and it would have been nice if Sigil's Report thing would list all of the used html tags.

[KevinH]

FWIW, There is no such thing as "unused" html tags. Under the html5 spec you can actually define your own tags. These can be processed using javascript as well.

[hobnail]

Originally Posted by KevinH

FWIW, There is no such thing as "unused" html tags. Under the html5 spec you can actually define your own tags. These can be processed using javascript as well.

I was thinking along the lines of the book using things like blockquote when it clearly wasn't a quote, or h5 for bolding.

[hobnail]

Originally Posted by KevinH

FWIW, There is no such thing as "unused" html tags. Under the html5 spec you can actually define your own tags. These can be processed using javascript as well.

Do you need to provide a schema?

[JSWolf]

Originally Posted by DNSB

I suppose cssRemoveUnusedSelectors plugin could be modified so undefined classes would be added to the stylesheet as a blank selector ( .whatever {} ) but not sure how much easier that would make the job. Are you volunteering to code and test this?

Thing is, there are a lot of eBooks that have nonexistent classes in the HTML. Some of those classes ae used in place of an ID. The others, I have no idea why they are there or why the CSS is missing those classes.

[mcdummy]

Thanks to comments by @DNSB and @hobnail.

It would be good to have both an information showing the undefined/non-existing classes and an option to remove those of them that a user does not want to keep.

A manual removal could be quite complicated, since I've seen constructions like class="class1 class2 ... classN", which makes it difficult to remove a specific class (even with regex) if it has a "conventional" name like "center" or the name of class2 (e.g., heading, author) is also a part of classN (e.g., subheading, co-author).

An option for the generation of empty classes for the ones that are kept would be the icing on the cake.

I don't know if this already exists in the plugin, but since there's a discussion about code additions.

I've seen style sheets contain class definitions two or more times. Therefore, it would be good, if these definitions were merged.

I further noticed that sometimes classes contain the same instruction several times but with different values, e.g., "text-align: left" followed later by "text-align: right". Since only the last definition will be applied, it would be advantageous to remove the first.

[wrCisco]

Hi mcdummy,
I'd rather think about providing a different plugin that could automatically remove unmatched classes in xml/xhtml than modifying this one. That's because this plugin is designed to run as safely as possible on as many epubs out there as possible, and in doing so it changes absolutely nothing outside of css files. Adding this feature would open a whole new set of issues and edge cases to be worried about.

If (but that's a big if) I find the time in the next days I'll try to put something together (but if someone else wants to step up, please feel free to do so).

About the other suggestions, I find them interesting, and I'll think about them a bit more, although I'm not totally convinced. These are my thoughts for now.

Just showing the classes unmatched by a selector is already done by the Reports tool as DNSB pointed out.

About merging rulesets, I think that's not impossible, but that's not totally safe either:

.classA {}
.classB { color: red }
.classA { color: blue }

is not the same as

.classA { color: blue }
.classB { color: red }

for a tag like <p class="classA classB">.

Originally Posted by mcdummy

I further noticed that sometimes classes contain the same instruction several times but with different values, e.g., "text-align: left" followed later by "text-align: right". Since only the last definition will be applied, it would be advantageous to remove the first.

True, unless the rendering engine of the epub reader decides that the last property has an invalid value: in that case it will use (probably) the first one.

@hobnail: I'm not sure I understood your last posts: do you have a specific proposal or were you simply backing the request of mcdummy?

[mcdummy]

Originally Posted by wrCisco

I'd rather think about providing a different plugin that could automatically remove unmatched classes in xml/xhtml than modifying this one. That's because this plugin is designed to run as safely as possible on as many epubs out there as possible, and in doing so it changes absolutely nothing outside of css files. Adding this feature would open a whole new set of issues and edge cases to be worried about.

I'm happy with a separate plugin, if it both indicates the unmatched classes and provides an option to select those that should be deleted. Automatic deletion is a bit disadvantageous, since I often want to keep some of the classes and add the definitions to the css.

Originally Posted by wrCisco

Just showing the classes unmatched by a selector is already done by the Reports tool as DNSB pointed out.

Combining the report and deletion in one tool makes things easier.

Originally Posted by wrCisco

About merging rulesets, I think that's not impossible, but that's not totally safe either:

.classA {}
.classB { color: red }
.classA { color: blue }

is not the same as

.classA { color: blue }
.classB { color: red }

for a tag like <p class="classA classB">.

Was not aware of this problem. It would be good to be informed about double defintions either of classes or within a class. An option to merge or delete double definitions would be great.

[wrCisco]

Originally Posted by mcdummy

I'm happy with a separate plugin, if it both indicates the unmatched classes and provides an option to select those that should be deleted. Automatic deletion is a bit disadvantageous, since I often want to keep some of the classes and add the definitions to the css.

Hi, I uploaded last week the plugin you requested (here's the thread) and forgot to mention it here...

Meanwhile, I uploaded version 0.3.2 of this plugin with an icon for displaying in Sigil.