Our current interfaces to connect data (lazily) to components such as Grid and ComboBox have shortcomings that make it difficult or impossible to use in certain situations, such as when the backend only allows paged access or when calculating the size of resultset is slow or not supported at all.

Commenting / Activity log experience

Team communication capabilities like TaskMob can be added to your app with off the shelf components

The dropdown does not work on Vite

Please see example repo below. The code is in the HelloWorld Vue component.

just clone, install and run dev

https://github.com/ais-one/vite-vaadin

I'm not using any of the Vaadin Pro web components, but I keep seeing the message over my application that I need to go get the license.

Here is the piece of code which lists all of the components I am using:

Promise.all([
customElements.whenDefined("vaadin-list-box"),
customElements.whenDefined("vaadin-item"),
customElements.whenDefined("vaadin-button"),
customElements.whenDefined("vaadin-grid")
])

And I import them individually.
I do not use grid pro, only grid.

What should I do?

https://travis-ci.org/vaadin/vaadin/builds/424270132

It would be great to get an overview of the status which components have been (re-)developed already based on lit-html and lit-element on this page: https://github.com/vaadin/vaadin

Thanks.

Similarly to vaadin-core/vaadin-core.html import, we should have a vaadin/vaadin.html import which imports all the components in the package.

Hi,

I found a mistake on your website, it seems that "Customer stories" redirects to "/directory" instead of "/customer-stories".
Same issue on my phone so I don't think it's an issue on my side.

Hi,

I am using a Vaadin controls in our application (lit-element and polymer). I saw the styles of vaadin component are rendered in head tag under "dom-module". I am want to confirm that why these styles are rendered in head tag rather than being the part of shadow-dom.

Also, when a route is changed and vaadin components are removed from dom then these styles are still there in head tag.

Is there a way to render these styles as a part of shadow dom rather than head tag.

Please suggest us.

Thanks.

Issue with grid when height-by-rows is enabled.
Scroll is blinking and cannot drop dragged item below last item.
Workaround is to add footer, but it's impossible to change height of it.

Support RTL in all components and switch between LTR and RTL with one line of Java code.

Hi,

We are trying to create Angular wrapper for Vaadin WebComponents using Angular directives.

Why we are doing this?

• Type checking in templates can happen at compile time
• Can avoid CUSTOM_ELEMENTS_SCHEMA usage
• Can think the possibility of providing test harness specific to component in Angular

What we did ?

1. We wrapped Vaadin-Checkbox by extending it. We are yet to delegate properties, events etc.

import { Component, NgZone } from '@angular/core';
import {CheckboxElement} from '@vaadin/vaadin-checkbox/src/vaadin-checkbox.js'
import { ChangeDetectorRef, ElementRef } from '@angular/core';
import '@vaadin/vaadin-checkbox';

@Component({
  selector: 'vaadin-checkbox',
  template: '<ng-content></ng-content>',
})
export class CheckboxComponent extends CheckboxElement {
  protected el: HTMLElement;

  constructor(c: ChangeDetectorRef, r: ElementRef, protected z: NgZone) {
    super(c, r, z); // Here we tried super(); also
    c.detach();
    this.el = r.nativeElement;
  }
}

2. We created a new Angular app and used the vaadin-checkbox directive in the app.component.html

<vaadin-checkbox >Ok</vaadin-checkbox>

3. We are seeing the vaadin-checkbox rendered but an error observed.
   

core.js:5809 ERROR TypeError: Illegal constructor
    at new PropertiesChanged (properties-changed.js:166)
    at new PropertyAccessors (property-accessors.js:115)
    at new TemplateStamp (template-stamp.js:171)
    at new PropertyEffects (property-effects.js:1107)
    at new PropertiesMixin (properties-mixin.js:113)
    at new PolymerElement (element-mixin.js:522)
    at new GestureEventListeners (gesture-event-listeners.js:38)
    at new VaadinThemePropertyMixin (vaadin-theme-property-mixin.js:4)
    at new VaadinThemableMixin (vaadin-themable-mixin.js:8)
    at new VaadinTabIndexMixin (vaadin-control-state-mixin.js:11)

We tried passing super() and with arguments but still getting this illegal constructor.

Could you please suggest how we can extend Vaadin control at Angular side?

Regards
Basanth

Hi
Maybe you want to register the namespace "vaadin" here with a pull request?
https://github.com/nuxodin/web-namespace-registry

**java.lang.IllegalStateException: Failed to update the Flow imports file 'C:\Users\RICARDO\tps\target\frontend\generated-flow-imports.js'

Operating System - Windows 10 and CentOs 7.**

2019-11-14 20:59:08.864 INFO 13960 --- [ main] com.ui.BlockchainApplication : Starting BlockchainApplication v0.0.1-SNAPSHOT on RECC with PID 13960 (C:\Users\RICARDO\tps\blockchain.jar started by RICARDO in C:\Users\RICARDO\tps)
2019-11-14 20:59:08.874 INFO 13960 --- [ main] com.ui.BlockchainApplication : No active profile set, falling back to default profiles: default
2019-11-14 20:59:10.607 INFO 13960 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Bootstrapping Spring Data repositories in DEFAULT mode.
2019-11-14 20:59:11.098 INFO 13960 --- [ main] .s.d.r.c.RepositoryConfigurationDelegate : Finished Spring Data repository scanning in 474ms. Found 2 repository interfaces.
2019-11-14 20:59:11.875 INFO 13960 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration' of type [org.springframework.transaction.annotation.ProxyTransactionManagementConfiguration$$EnhancerBySpringCGLIB$$8509b87a] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2019-11-14 20:59:11.921 INFO 13960 --- [ main] trationDelegate$BeanPostProcessorChecker : Bean 'org.springframework.hateoas.config.HateoasConfiguration' of type [org.springframework.hateoas.config.HateoasConfiguration$$EnhancerBySpringCGLIB$$48a05ac] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)
2019-11-14 20:59:13.318 INFO 13960 --- [ main] o.s.b.w.embedded.tomcat.TomcatWebServer : Tomcat initialized with port(s): 9090 (http)
2019-11-14 20:59:13.367 INFO 13960 --- [ main] o.apache.catalina.core.StandardService : Starting service [Tomcat]
2019-11-14 20:59:13.368 INFO 13960 --- [ main] org.apache.catalina.core.StandardEngine : Starting Servlet engine: [Apache Tomcat/9.0.26]
2019-11-14 20:59:13.668 INFO 13960 --- [ main] o.a.c.c.C.[Tomcat].[localhost].[/] : Initializing Spring embedded WebApplicationContext
2019-11-14 20:59:13.668 INFO 13960 --- [ main] o.s.web.context.ContextLoader : Root WebApplicationContext: initialization completed in 4681 ms
2019-11-14 20:59:20.830 INFO 13960 --- [ main] c.v.f.s.VaadinServletContextInitializer : Search for subclasses and classes with annotations took 6 seconds
2019-11-14 20:59:20.838 INFO 13960 --- [ main] c.v.f.server.startup.DevModeInitializer : Starting dev-mode updaters in C:\Users\RICARDO\tps folder.
2019-11-14 20:59:20.857 INFO 13960 --- [ main] dev-updater : Scanning classes to find frontend configurations and dependencies...
2019-11-14 20:59:22.285 INFO 13960 --- [ main] dev-updater : Visited 982 classes. Took 1428 ms.
2019-11-14 20:59:22.337 INFO 13960 --- [ main] dev-updater : Skipping npm install.
2019-11-14 20:59:22.337 INFO 13960 --- [ main] dev-updater : Copying frontend resources from jar files ...
2019-11-14 20:59:22.339 INFO 13960 --- [ main] dev-updater : Visited 0 resources. Took 1 ms.
2019-11-14 20:59:22.375 ERROR 13960 --- [ main] o.a.c.c.C.[Tomcat].[localhost].[/] : Exception sending context initialized event to listener instance of class [com.vaadin.flow.spring.VaadinServletContextInitializer$DevModeServletContextListener]

java.lang.IllegalStateException: Failed to update the Flow imports file 'C:\Users\RICARDO\tps\target\frontend\generated-flow-imports.js'
at com.vaadin.flow.server.frontend.TaskUpdateImports.execute(TaskUpdateImports.java:136) ~[flow-server-2.0.17.jar!/:2.0.17]
at com.vaadin.flow.server.frontend.NodeTasks.execute(NodeTasks.java:372) ~[flow-server-2.0.17.jar!/:2.0.17]
at com.vaadin.flow.server.startup.DevModeInitializer.initDevModeHandler(DevModeInitializer.java:322) ~[flow-server-2.0.17.jar!/:2.0.17]
at com.vaadin.flow.spring.VaadinServletContextInitializer$DevModeServletContextListener.contextInitialized(VaadinServletContextInitializer.java:323) ~[vaadin-spring-12.0.6.jar!/:na]
at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4683) [tomcat-embed-core-9.0.26.jar!/:9.0.26]
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5146) [tomcat-embed-core-9.0.26.jar!/:9.0.26]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) [tomcat-embed-core-9.0.26.jar!/:9.0.26]
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1384) [tomcat-embed-core-9.0.26.jar!/:9.0.26]
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1374) [tomcat-embed-core-9.0.26.jar!/:9.0.26]
at java.util.concurrent.FutureTask.run(Unknown Source) [na:1.8.0_45]
at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75) [tomcat-embed-core-9.0.26.jar!/:9.0.26]
at java.util.concurrent.AbstractExecutorService.submit(Unknown Source) [na:1.8.0_45]
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:909) [tomcat-embed-core-9.0.26.jar!/:9.0.26]
at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:841) [tomcat-embed-core-9.0.26.jar!/:9.0.26]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) [tomcat-embed-core-9.0.26.jar!/:9.0.26]
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1384) [tomcat-embed-core-9.0.26.jar!/:9.0.26]
at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1374) [tomcat-embed-core-9.0.26.jar!/:9.0.26]
at java.util.concurrent.FutureTask.run(Unknown Source) [na:1.8.0_45]
at org.apache.tomcat.util.threads.InlineExecutorService.execute(InlineExecutorService.java:75) [tomcat-embed-core-9.0.26.jar!/:9.0.26]
at java.util.concurrent.AbstractExecutorService.submit(Unknown Source) [na:1.8.0_45]
at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:909) [tomcat-embed-core-9.0.26.jar!/:9.0.26]
at org.apache.catalina.core.StandardEngine.startInternal(StandardEngine.java:262) [tomcat-embed-core-9.0.26.jar!/:9.0.26]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) [tomcat-embed-core-9.0.26.jar!/:9.0.26]
at org.apache.catalina.core.StandardService.startInternal(StandardService.java:421) [tomcat-embed-core-9.0.26.jar!/:9.0.26]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) [tomcat-embed-core-9.0.26.jar!/:9.0.26]
at org.apache.catalina.core.StandardServer.startInternal(StandardServer.java:932) [tomcat-embed-core-9.0.26.jar!/:9.0.26]
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:183) [tomcat-embed-core-9.0.26.jar!/:9.0.26]
at org.apache.catalina.startup.Tomcat.start(Tomcat.java:459) [tomcat-embed-core-9.0.26.jar!/:9.0.26]
at org.springframework.boot.web.embedded.tomcat.TomcatWebServer.initialize(TomcatWebServer.java:105) [spring-boot-2.1.9.RELEASE.jar!/:2.1.9.RELEASE]
at org.springframework.boot.web.embedded.tomcat.TomcatWebServer.(TomcatWebServer.java:86) [spring-boot-2.1.9.RELEASE.jar!/:2.1.9.RELEASE]
at org.springframework.boot.web.embedded.tomcat.TomcatServletWebServerFactory.getTomcatWebServer(TomcatServletWebServerFactory.java:416) [spring-boot-2.1.9.RELEASE.jar!/:2.1.9.RELEASE]
at org.springframework.boot.web.embedded.tomcat.TomcatServletWebServerFactory.getWebServer(TomcatServletWebServerFactory.java:180) [spring-boot-2.1.9.RELEASE.jar!/:2.1.9.RELEASE]
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.createWebServer(ServletWebServerApplicationContext.java:180) [spring-boot-2.1.9.RELEASE.jar!/:2.1.9.RELEASE]
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.onRefresh(ServletWebServerApplicationContext.java:153) [spring-boot-2.1.9.RELEASE.jar!/:2.1.9.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:543) [spring-context-5.1.10.RELEASE.jar!/:5.1.10.RELEASE]
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:141) [spring-boot-2.1.9.RELEASE.jar!/:2.1.9.RELEASE]
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:744) [spring-boot-2.1.9.RELEASE.jar!/:2.1.9.RELEASE]
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:391) [spring-boot-2.1.9.RELEASE.jar!/:2.1.9.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:312) [spring-boot-2.1.9.RELEASE.jar!/:2.1.9.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1215) [spring-boot-2.1.9.RELEASE.jar!/:2.1.9.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1204) [spring-boot-2.1.9.RELEASE.jar!/:2.1.9.RELEASE]
at com.ui.BlockchainApplication.main(BlockchainApplication.java:10) [classes!/:0.0.1-SNAPSHOT]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[na:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[na:1.8.0_45]
at java.lang.reflect.Method.invoke(Unknown Source) ~[na:1.8.0_45]
at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48) [blockchain.jar:0.0.1-SNAPSHOT]
at org.springframework.boot.loader.Launcher.launch(Launcher.java:87) [blockchain.jar:0.0.1-SNAPSHOT]
at org.springframework.boot.loader.Launcher.launch(Launcher.java:51) [blockchain.jar:0.0.1-SNAPSHOT]
at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:52) [blockchain.jar:0.0.1-SNAPSHOT]
Caused by: java.lang.IllegalStateException:

Failed to find the following css files in the node_modules or C:\Users\RICARDO\tps\.\frontend directory tree:
- ./styles/view-styles.css
- ./styles/shared-styles.css
Check that they exist or are installed. If you use a custom directory for your resource files instead of the default frontend folder then make sure it's correctly configured (e.g. set 'vaadin.frontend.frontend.folder' property)

at com.vaadin.flow.server.frontend.TaskUpdateImports.getCssLines(TaskUpdateImports.java:213) ~[flow-server-2.0.17.jar!/:2.0.17]
at com.vaadin.flow.server.frontend.TaskUpdateImports.getMainJsContent(TaskUpdateImports.java:146) ~[flow-server-2.0.17.jar!/:2.0.17]
at com.vaadin.flow.server.frontend.TaskUpdateImports.execute(TaskUpdateImports.java:133) ~[flow-server-2.0.17.jar!/:2.0.17]
... 49 common frames omitted

2019-11-14 20:59:22.383 ERROR 13960 --- [ main] o.apache.catalina.core.StandardContext : One or more listeners failed to start. Full details will be found in the appropriate container log file
2019-11-14 20:59:22.384 ERROR 13960 --- [ main] o.apache.catalina.core.StandardContext : Context [] startup failed due to previous errors
2019-11-14 20:59:22.945 INFO 13960 --- [ main] o.apache.catalina.core.StandardService : Stopping service [Tomcat]
2019-11-14 20:59:22.960 WARN 13960 --- [ main] ConfigServletWebServerApplicationContext : Exception encountered during context initialization - cancelling refresh attempt: org.springframework.context.ApplicationContextException: Unable to start web server; nested exception is org.springframework.boot.web.server.WebServerException: Unable to start embedded Tomcat
2019-11-14 20:59:22.972 INFO 13960 --- [ main] ConditionEvaluationReportLoggingListener :

Error starting ApplicationContext. To display the conditions report re-run your application with 'debug' enabled.
2019-11-14 20:59:22.974 ERROR 13960 --- [ main] o.s.boot.SpringApplication : Application run failed

org.springframework.context.ApplicationContextException: Unable to start web server; nested exception is org.springframework.boot.web.server.WebServerException: Unable to start embedded Tomcat
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.onRefresh(ServletWebServerApplicationContext.java:156) ~[spring-boot-2.1.9.RELEASE.jar!/:2.1.9.RELEASE]
at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:543) ~[spring-context-5.1.10.RELEASE.jar!/:5.1.10.RELEASE]
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.refresh(ServletWebServerApplicationContext.java:141) ~[spring-boot-2.1.9.RELEASE.jar!/:2.1.9.RELEASE]
at org.springframework.boot.SpringApplication.refresh(SpringApplication.java:744) [spring-boot-2.1.9.RELEASE.jar!/:2.1.9.RELEASE]
at org.springframework.boot.SpringApplication.refreshContext(SpringApplication.java:391) [spring-boot-2.1.9.RELEASE.jar!/:2.1.9.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:312) [spring-boot-2.1.9.RELEASE.jar!/:2.1.9.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1215) [spring-boot-2.1.9.RELEASE.jar!/:2.1.9.RELEASE]
at org.springframework.boot.SpringApplication.run(SpringApplication.java:1204) [spring-boot-2.1.9.RELEASE.jar!/:2.1.9.RELEASE]
at com.ui.BlockchainApplication.main(BlockchainApplication.java:10) [classes!/:0.0.1-SNAPSHOT]
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) ~[na:1.8.0_45]
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) ~[na:1.8.0_45]
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) ~[na:1.8.0_45]
at java.lang.reflect.Method.invoke(Unknown Source) ~[na:1.8.0_45]
at org.springframework.boot.loader.MainMethodRunner.run(MainMethodRunner.java:48) [blockchain.jar:0.0.1-SNAPSHOT]
at org.springframework.boot.loader.Launcher.launch(Launcher.java:87) [blockchain.jar:0.0.1-SNAPSHOT]
at org.springframework.boot.loader.Launcher.launch(Launcher.java:51) [blockchain.jar:0.0.1-SNAPSHOT]
at org.springframework.boot.loader.JarLauncher.main(JarLauncher.java:52) [blockchain.jar:0.0.1-SNAPSHOT]
Caused by: org.springframework.boot.web.server.WebServerException: Unable to start embedded Tomcat
at org.springframework.boot.web.embedded.tomcat.TomcatWebServer.initialize(TomcatWebServer.java:124) ~[spring-boot-2.1.9.RELEASE.jar!/:2.1.9.RELEASE]
at org.springframework.boot.web.embedded.tomcat.TomcatWebServer.(TomcatWebServer.java:86) ~[spring-boot-2.1.9.RELEASE.jar!/:2.1.9.RELEASE]
at org.springframework.boot.web.embedded.tomcat.TomcatServletWebServerFactory.getTomcatWebServer(TomcatServletWebServerFactory.java:416) ~[spring-boot-2.1.9.RELEASE.jar!/:2.1.9.RELEASE]
at org.springframework.boot.web.embedded.tomcat.TomcatServletWebServerFactory.getWebServer(TomcatServletWebServerFactory.java:180) ~[spring-boot-2.1.9.RELEASE.jar!/:2.1.9.RELEASE]
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.createWebServer(ServletWebServerApplicationContext.java:180) ~[spring-boot-2.1.9.RELEASE.jar!/:2.1.9.RELEASE]
at org.springframework.boot.web.servlet.context.ServletWebServerApplicationContext.onRefresh(ServletWebServerApplicationContext.java:153) ~[spring-boot-2.1.9.RELEASE.jar!/:2.1.9.RELEASE]
... 16 common frames omitted
Caused by: java.lang.IllegalStateException: StandardEngine[Tomcat].StandardHost[localhost].TomcatEmbeddedContext[] failed to start
at org.springframework.boot.web.embedded.tomcat.TomcatWebServer.rethrowDeferredStartupExceptions(TomcatWebServer.java:169) ~[spring-boot-2.1.9.RELEASE.jar!/:2.1.9.RELEASE]
at org.springframework.boot.web.embedded.tomcat.TomcatWebServer.initialize(TomcatWebServer.java:108) ~[spring-boot-2.1.9.RELEASE.jar!/:2.1.9.RELEASE]
... 21 common frames omitted

Adds a new column type that makes the cells on that column editable inline. (Double)clicking a cells turns the cell content into an editor component that gets its value from the row item's sub-property defined by the columns path.

Closing the editor will make grid emit an event specific to this feature so that application logic can make necessary changes to the data.

Navigating between the cells of editable columns (while editing) can be done by (shift) tabbing.

From time to time, users are asking us about free and pro parts of our offering.

Question: vaadin/vaadin-login#50 (comment)

How are make-it-free decisions made? Are there specific criteria for a component to meet, or random chance during team discussion, or...

Answer: vaadin/vaadin-login#50 (comment)

It is more of a case-by-case matter (... and some details about the specific case)

This is probably not what the users actually expect. It would be nice to have a clear strategy documented on the website and linked from each of the PRO component repositories.

It would be extremely nice to get an IDE auto complete supported for the packaged web components on the npm repo. When I import the @vaadin/vaadin, I don't get any support at least in VS Code. Such things as showing the properties inside of the @vaadin/vaadin-progress-bar would be fantastic so I didn't have to go check the docs every time.

Sorry if this isn't the right place, feel free to point me elsewhere!