Bugzilla

These are getting misformatted by prettier v3, and it's about time we stop using them anyway. `link` elements are more widely recognized by tooling, and have more features than XML PIs.

(For instance, using "normal" `link` attributes with their `media` attributes would provide a neat way to e.g. include platform-specific styles in a way that doesn't require ifdefs or media queries combined with @import in a single shared sheet, for instance.)

It's worth noting that not all our consumers live in markup, cf. https://searchfox.org/mozilla-central/rev/d265ec4f5fdcb5ad0c06636c5ac010ef4ff7eb89/toolkit/modules/SubDialog.sys.mjs#111-121 .

These are getting misformatted by prettier v3, and it's about time we stop using them anyway. `link` elements are more widely recognized by tooling, and have more features than XML PIs.

(For instance, using "normal" `link` elements with their `media` attributes would provide a neat way to e.g. include platform-specific styles in a way that doesn't require ifdefs or media queries combined with @import in a single shared sheet, for instance.)

It's worth noting that not all our consumers live in markup, cf. https://searchfox.org/mozilla-central/rev/d265ec4f5fdcb5ad0c06636c5ac010ef4ff7eb89/toolkit/modules/SubDialog.sys.mjs#111-121 .

These are getting misformatted by prettier v3, and it's about time we stop using them anyway. `link` elements are more widely recognized by tooling, and have more features than XML PIs.

(For instance, using "normal" `link` elements with their `media` attributes would provide a neat way to e.g. include platform-specific styles in a way that doesn't require ifdefs or media queries combined with @import in a single shared sheet.)

It's worth noting that not all our consumers live in markup, cf. https://searchfox.org/mozilla-central/rev/d265ec4f5fdcb5ad0c06636c5ac010ef4ff7eb89/toolkit/modules/SubDialog.sys.mjs#111-121 .