Hi,

while debugging a display issue with IOS I encountered that the default values don't look right:

:host([theme~="margin"]) {
    margin: 1em;
}
:host([theme~="padding"]) #grid-layout-element {
    padding: 1em 1em 0 1em;
}
:host([theme~="margin"]) #grid-layout-element {
    margin: var(--lumo-space-m);
}
:host([theme~="padding"]) #grid-layout-element {
    padding: var(--lumo-space-m);
}

Theme "margin" sets margin on two elements => it gets way too big.
Theme "padding" has 2 css styles targeting grid-layout-element.

Can you tell me when the Vaadin 24 compatible version 3.0.0. will be available in maven central / vaadin add-on repos please?

Code: Demo Code
Application Server: Tomcat 9.0 or Jetty
Vaadin Version: 14.0.1
Grid Layout Version: 2.0.0.beta1
Browser: Any browser with the latest version (Windows)

Note: There is not any error on the screen or on the browser console. There is only a blank window.

and probably others

In order to create responsive grids, it would be nice to be able to set responsive steps as is possible with form layouts (https://vaadin.com/components/vaadin-form-layout/java-examples)
Since it is not possible to add @media selectors inline (directly on the element), a possible workaround would be to create a separate DOM style object and use it to hold the various css and variants for the grid as suggested in the second answer to https://stackoverflow.com/questions/9808233/is-it-possible-to-put-css-media-rules-inline
https://developer.mozilla.org/en-US/docs/Web/HTML/Element/style

Eclipse signals dead code in GridLayout.java routine setArea.

If area is null, there will be a null pointer exception at line 277, and code at line 280 will never be reached.

Suggestion: message should be "a maximum of 4 arguments for row/columns can be passed"

Hi, im using the new version of vaadin with npm and spring in Intellij Idea, but when i put the maven installation in pom file.

When i run, i recive this message

i have this in may YML

vaadin:
compatibilityMode : false

Couldn't find the definition of the element with tag 'grid-layout' in any template file declared using '@jsmodule'

Because of

<!-- Added to provide logging output as Vaadin uses -->
<!-- the unbound SLF4J no-operation (NOP) logger implementation -->
<dependency>
    <groupId>org.slf4j</groupId>
    <artifactId>slf4j-simple</artifactId>
</dependency>

the application fails to start because there are multiple

SLF4J: Class path contains multiple SLF4J providers.
SLF4J: Found provider [org.slf4j.simple.SimpleServiceProvider@3569fc08]
SLF4J: Found provider [ch.qos.logback.classic.spi.LogbackServiceProvider@20b12f8a]
SLF4J: See https://www.slf4j.org/codes.html#multiple_bindings for an explanation.
SLF4J: Actual provider is of type [org.slf4j.simple.SimpleServiceProvider@3569fc08]
[main] INFO org.springframework.boot.devtools.restart.RestartApplicationListener - Restart disabled due to an agent-based reloader being active
Exception in thread "main" java.lang.IllegalArgumentException: LoggerFactory is not a Logback LoggerContext but Logback is on the classpath. Either remove Logback or the competing implementation (class org.slf4j.simple.SimpleLoggerFactory loaded from file:/C:/Users/simon/.m2/repository/org/slf4j/slf4j-simple/2.0.7/slf4j-simple-2.0.7.jar). If you are using WebLogic you will need to add 'org.slf4j' to prefer-application-packages in WEB-INF/weblogic.xml: org.slf4j.simple.SimpleLoggerFactory
at org.springframework.util.Assert.instanceCheckFailed(Assert.java:713)
at org.springframework.util.Assert.isInstanceOf(Assert.java:632)
at org.springframework.boot.logging.logback.LogbackLoggingSystem.getLoggerContext(LogbackLoggingSystem.java:381)
at org.springframework.boot.logging.logback.LogbackLoggingSystem.beforeInitialize(LogbackLoggingSystem.java:122)
at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationStartingEvent(LoggingApplicationListener.java:238)
at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationEvent(LoggingApplicationListener.java:220)
at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:176)
at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:169)
at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:143)
at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:131)
at org.springframework.boot.context.event.EventPublishingRunListener.multicastInitialEvent(EventPublishingRunListener.java:136)
at org.springframework.boot.context.event.EventPublishingRunListener.starting(EventPublishingRunListener.java:75)
at org.springframework.boot.SpringApplicationRunListeners.lambda$starting$0(SpringApplicationRunListeners.java:54)
at java.base/java.lang.Iterable.forEach(Iterable.java:75)
at org.springframework.boot.SpringApplicationRunListeners.doWithListeners(SpringApplicationRunListeners.java:118)
at org.springframework.boot.SpringApplicationRunListeners.starting(SpringApplicationRunListeners.java:54)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:302)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1304)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1293)