View Single Post
Old 01-07-2021, 08:29 PM   #51
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,930
Karma: 6361444
Join Date: Nov 2009
Device: many
Regarding @import issues with CSSParser:

I tried the following variations at the top of a test css file:

@import url(../hello/junk.css);
@import "../hello/junk1.css";
@import url("../hello/junk2.css");

Other than the missing space after @import the css code seemed to be parsed properly.


So I am now confused as to what you meant by @import "not being recognized".

Do you mean the @import command was not parsed into appropriate pieces or do you mean that no import / inclusion of the specified spreadshhet was done. If the latter, that is expected behaviour of the parser. It is not the parser that should handle any physical inclusion, just parsing the request. Upstream code from the parser would be responsible for locating the file and actually including it and that typically is done only when used for rendering.

So when you get a free moment would you explain what you meant.

Thanks.

Last edited by KevinH; 01-07-2021 at 08:48 PM.
KevinH is offline   Reply With Quote