Investigate if CSS specificity is correct when using opinionated layers

[Zn4rK]

Remix adds their own "critical css". Vite does the same. Almost. This is to avoid FOUC:
remix-run/remix#8070 (reply in thread)

One solution to this problem could be to use "opinionated layers" in dev mode for Remix (and potentially Vite).

The relevant function that figures out specificity, that could be incorrect, if the same CSS block is added twice:

navita/packages/engine/src/helpers/getPropertyPriority.ts

Line 203 in 81f962c

export const getPropertyPriority = (property: string) => longhands.includes(property) ? 2 : 1;

Note: The root cause is that the same CSS block is added twice.

[Zn4rK]

The CSS specificity is correct. There was however another bug due to how Remix inlines criticalCss. But a fix for that is on the way.