-
### Description of the bug
No `theme` attribute is applied to the page root when a theme variant is applied with the `@Theme` annotation's `variant` parameter.
The variant starts working again wit…
-
### Description of the bug
Custom theme styles are not applied to embedded components in Express Build mode (Vaadin 24.0).
### Expected behavior
Embedded components are styled properly as any non-e…
-
### Description of the bug
Embedded components are not rendered properly in Express Build mode (Vaadin 24.0).
### Expected behavior
Embedded components are rendered and styles are applied.
…
-
### Description of the bug
I added `"strict": true` to the generated `tsconfig.json`, but despite excluding `frontend/generated/jar-resources/**`, the TypeScript compiler still includes sources in …
-
### Description of the bug
In a pure Flow application (straight from https://start.vaadin.com/) I'm using the template approach for one component: so I have a Java Component (extends LitTemplate) and…
-
### Description of the bug
In one of our components we imported a Stylesheet like this:
import * as css from "./my-styles.css";
Upon starting the application Vite warns that this use of importing…
-
Maven and Gradle plugin should have the `frontend.hotdeploy` flag as a configuration that would be propagated to the `flow-build-info.json` file for development runtime configuration.
-
I get the following message continuously outputting to the console and it only stops when I restart membrane.
WARN HttpTransport:126 - Still waiting for running exchanges to finish. (Set <transpor…
-
- [plugin:vite:import-analysis] Failed to resolve import "@vaadin/vaadin-text-field/src/vaadin-text-area" from "frontend/generated/jar-resources/super-text-area.js". Does the file exist?
- setPrevent…
-
**Jetty version(s)**
12.0.0-SNAPSHOT
**Java version/vendor**
openjdk version "19.0.1" 2022-10-18
**OS type/version**
mac os
**Description**
Some of our tests fail to start jetty when usin…