### Description of the bug The loading order of CSS described in https://vaadin.com/docs/latest/advanced/css-loading-order is 1. The Lumo theme. 2. Application-specific bundled CSS added with a `@CssImport'. 3. Styles added on the Java side via Page::addStylesheet(). 4. Application-specific unbundled CSS added with @StyleSheet. 5. Parent theme. 6. Current theme. This works as expected when running with Vite except that `@CssImport` does not override the Lumo theme.  ### Expected behavior Lumo styles should always be only default styles and everything else should override ### Minimal reproducible example - ### Versions - Vaadin / Flow version: 24.0.0
Activity
fix: Import all document styles using style tags
fix: Import all document styles using style tags
fix: Import all document styles using style tags
fix: Import all document styles using style tags
fix: Import all document styles using style tags
fix: Import all document styles using style tags
fix: Import all document styles using style tags
fix: Import all document styles using style tags
fix: Import all document styles using style tags
fix: Import all document styles using style tags
fix: Import all document styles using style tags
fix: Import all document styles using style tags
fix: Import all document styles using style tags
fix: Import all document styles using style tags
fix: Import all document styles using style tags
fix: Import all document styles using style tags
fix: Import all document styles using style tags (#16247)
fix: Import all document styles using style tags
vaadin-bot commentedon Apr 4, 2023
This ticket/PR has been released with Vaadin 24.1.0.alpha2 and is also targeting the upcoming stable 24.1.0 version.