Bug 1659583 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

For more contexts, see bug 1659444.

Query that currently captures all of these: https://searchfox.org/mozilla-central/search?q=%25if&path=css .

There are broadly the following cases:

1. `%if 0`, especially for license headers. These can just be converted to normal comments.
2. CSS that can move from "shared" files to OS-specific files
3. CSS using `MENUBAR_CAN_AUTOHIDE`, which can probably switch to using an attribute on the root (moving the ifdef into browser.xhtml, where it's already used anyway)
4. CSS that is platform-specific and can switch to using an attribute, media query, or other mechanism
5. CSS that is inside the UA stylesheets. There we can use something like:

```css
/*
%ifdef MOZ_WIDGET_GTK
*/
...
/*
%endif
*/
```

to hide the preprocessor markup from a linter.
For more contexts, see bug 1659444.

Query that currently captures all of these: https://searchfox.org/mozilla-central/search?q=%25if&path=css .

There are broadly the following cases:

1. `%if 0`, especially for license headers. These can just be converted to normal comments. This is now covered by bug 1747459.
2. CSS that can move from "shared" files to OS-specific files
3. CSS using `MENUBAR_CAN_AUTOHIDE`, which can probably switch to using an attribute on the root (moving the ifdef into browser.xhtml, where it's already used anyway)
4. CSS that is platform-specific and can switch to using an attribute, media query, or other mechanism
5. CSS that is inside the UA stylesheets. There we can use something like:

```css
/*
%ifdef MOZ_WIDGET_GTK
*/
...
/*
%endif
*/
```

to hide the preprocessor markup from a linter.

Back to Bug 1659583 Comment 0