View Single Post
Old 01-10-2021, 01:31 PM   #63
KevinH
Sigil Developer
KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.KevinH ought to be getting tired of karma fortunes by now.
 
Posts: 8,860
Karma: 6120478
Join Date: Nov 2009
Device: many
Okay, the very latest version of cssparser2 (not yet posted) will now happily and detect errors of using a "{" in the @import, @charset, and @namespace and report them while trying to continue on gracefully without losing any css.

I have also removed a couple of unused functions from CSSUtils.cpp and .h

I will post a cssparser_v2.1.zip later in the week when I get more free time.

Thanks!

Quote:
Originally Posted by wrCisco View Post
With the new registered QMetaType and the support in EmbeddedPython.cpp, the direct conversion from QList<int> to QVariant now works great, thanks!

As for the @import rule, the problem now is if I write something plainly wrong, like
Code:
@import { src: url(cssprova.css); }
the parser doesn't raise an error, and the serialization ends up with something like this:
Code:
@import {;

}
KevinH is offline   Reply With Quote