View Single Post
Old 06-26-2020, 02:38 AM   #52
mcdummy
Connoisseur
mcdummy is a jewel in the roughmcdummy is a jewel in the roughmcdummy is a jewel in the roughmcdummy is a jewel in the roughmcdummy is a jewel in the roughmcdummy is a jewel in the roughmcdummy is a jewel in the roughmcdummy is a jewel in the roughmcdummy is a jewel in the roughmcdummy is a jewel in the roughmcdummy is a jewel in the rough
 
mcdummy's Avatar
 
Posts: 73
Karma: 7130
Join Date: Apr 2015
Device: PRS-T3
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.
mcdummy is offline   Reply With Quote