pdf.js/external/builder/fixtures/if-nested.css

/*#if TRUE*/
div {
  margin: 0;
  /*#if FALSE*/
  padding: 0;
  /*#endif*/
}
/*#endif*/

/*#if FALSE*/
p {
  margin: 0;
}
/*#endif*/
Use the regular `preprocess`-function for the CSS files as well An old shortcoming of the `preprocessCSS`-function is its complete lack of support for our "normal" defines, which makes it very difficult to have build-specific CSS rules. Recently we've started using specially crafted comments to remove CSS rules from the MOZCENTRAL build, but (ab)using the `preprocessCSS`-function in this way really doesn't feel great. However, it turns out to be surprisingly simple to instead use the "regular" `preprocess`-function for the CSS files as well. The only special-handling that's still necessary is the helper-function for dealing with CSS-imports, but apart from that everything seems to just work. One reason, as far as I can tell, for having a separate `preprocessCSS`-function was likely that we originally used lots of vendor-prefixed CSS rules in our CSS files. With improvements over the years, especially thanks to Autoprefixer and PostCSS, we've been able to remove almost all non-standard CSS rules and the need for special-casing the CSS parsing has mostly vanished. Please note: As part of testing this patch I've diffed the output of `gulp generic`, `gulp mozcentral`, and `gulp chromium` against the `master`-branch to check that there was no obvious breakage. 2022-05-08 05:00:54 +09:00			`/#if TRUE/`
			`div {`
			`margin: 0;`
			`/#if FALSE/`
			`padding: 0;`
			`/#endif/`
			`}`
			`/#endif/`

			`/#if FALSE/`
			`p {`
			`margin: 0;`
			`}`
			`/#endif/`