[KevinH]

That issue should now be fixed in Sigil master.

It was not their bug, but my interface bug as I chose to use raw css tokens character data to prevent replacements of escaped strings but did not clean them up before using them.

They are purposely left in raw data as a space after a selector segment but before the end must not be trimmed as it may indicate a compound selector.

FWIW, it was actually a lot of work to properly interface their css parser for our use both because it is a heavy callback design for speed and because it is designed to be actually used inside a browser and simply ignores anything it does not like (which is what the spec tells it to do)!

But in Sigil we need feedback on errors in some way to prevent running a reformat when the css itself is broken in someway, possibly ruining it. And we do not want to change the meaning a whole selector because of a missing ";" at the end of one of the properties values.

Either way, this should now be fixed.

I never thought to repeatedly run the reformatter during my testing. I should have.

Thank you for testing it and finding that bug!