vaadin/web-components

Vaadin has a high quality component set for building mobile and desktop web applications in modern browsers

Kari Söderholm

@Haprog

First I'll check if I can reproduce it in our demos, then need to create and issue in GitHub and then we can fix it.

Thanks for being able to help with reproducing!

I can't reproduce it in the demos at https://cdn.vaadin.com/vaadin-date-picker/4.0.3/demo/#date-picker-basic-demos Maybe it's more likely to appear only on more complex or heavier pages.

Kari Söderholm

@Haprog

Would be good if we can make some simple way to reproduce it so we can easily validate the fix too (without relying on the issue only happening on some third party site).

Walter Laurito

@lauritowal

I need to wait for an upgrade right now, before I can try it out again. I'll let you know if I can reproduce it later.

Kari Söderholm

@Haprog

Thanks. Please let me know if the workaround above fixes it for you.

Or if you can apply the workaround on the site, I can test in Simulator again.

But there might be some other issue too since you had the screenshot of it being broken on Chrome too.

Was that screenshot from your user/customer or from you? Do you know which version of Chrome is that?

It would be good to be able to reproduce it on Chrome too (if it really is an issue there, and not just an old Chrome version)

sdyalor

@sdyalor

@sdyalor
Hi everiyone
What is the alternative to componentDidMount() on Lit-Element?

YuanYuan Liu

@mgenware

@sdyalor i believe it's firstUpdated

Walter Laurito

@lauritowal

@Haprog. Hi Kari. Thanks for your help again. Unfortunately, the workaround did not fix our problem. We still notice the problem on the Iphone.

sdyalor

@sdyalor

Mgen

thankyou

Kari Söderholm

@Haprog

@lauritowal Hmm ok, then it might be some other issue. It might be some race condition depending on in which order some dependencies on the page load or something else on the page affecting the initial render of the date picker overlay. If you can somehow isolate the issue to make a small application that reproduces the problem (if it is a problem with the component itself) it would help us to make a fix.

Tomi Virkki

@tomivirkki

@lauritowal Looks like the issue reproduces locally also but only on material theme.

Tomi Virkki

@tomivirkki

We'll take a closer look at why the date picker overlay doesn't work in this particular case (Material theme on iOS 12 Safari). For now you can include the following snippet somewhere in your app (index.html for example) to workaround the issue.

<dom-module id="material-date-picker-overlay-animation" theme-for="vaadin-date-picker-overlay">
  <template>
    <style>
      @keyframes material-overlay-animation {
        100% {
          opacity: 1;
        }
      }

      :host([opening]),
      :host([closing]) {
        animation: 0.1s material-overlay-animation;
      }
    </style>
  </template>
</dom-module>

Tomi Virkki

@tomivirkki

Filed the issue in vaadin/vaadin-date-picker#676

Walter Laurito

@lauritowal

Hi guys @tomivirkki @Haprog Thanks for your help! I will try the workaround and let you know.

sdyalor

@sdyalor

Hey

I need serious help ;c

I got a table in server without relations, to display data there is a query with to much unions

fetch each table is more efficient

but i got a trouble rendering data with VaadinGrid

how can i reender Columns as table description

all data is in redux

here is the implementation

https://pwa.sdyalor.me/view4

Can someone help me with this ;c, I was thinking, creating a ViewArray maping all tables but dont know ;c

Pekka Maanpää

@pekam

Hi, @sdyalor! I'm not sure that I understand your issue. You want some kind of custom rendering of data? In that case, take a look at three demos here: https://vaadin.com/components/vaadin-grid/html-examples/grid-basic-demos
It looks like you have used the path property on columns to display the data. I suggest you to take a look at the second demo on the page I linked, which shows how to implement a renderer function for a column.

Mark Garrett

@moderndeveloperllc

Quick question: Anyway to have the label on <vaadin-checkbox-group> to be to the left instead of above the checkboxes?

sdyalor

@sdyalor

Ahm, my issue is how to get component render quick

i have performance issues ;c

Giovanni Lovato

@heruan

Guys I’m losing my mind: where this _setInputs is being defined?!

Giovanni Lovato

@heruan

Okay, seems like it’s a dynamic call handled by Polymer’s PropertyEffects :relieved:

Rajul Vishwakarma

@rajul3199

Failed to execute goal org.eclipse.jetty:jetty-maven-plugin:9.4.15.v20190215:run (default-cli) on project exercises-intro: Failure

i am having this problem when i was installing vaadin

please help me

Tulio Garcia

@tulioag

Hi @rajul3199 . That just means that mvn jetty:runfailed. Can you post the full error message?

Rajul Vishwakarma

@rajul3199

@tulioag

Failed to execute goal org.eclipse.jetty:jetty-maven-plugin:9.4.15.v20190215:run (default-cli) on project exercises-intro: Failure

This is the full error

Tulio Garcia

@tulioag

@rajul3199 , can you post the project or at least the pom.xml?

Rajul Vishwakarma

@rajul3199

@tulioag <?xml version="1.0" encoding="UTF-8"?>

<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<groupId>com.vaadin.trainings.intro</groupId>
<artifactId>exercises-intro</artifactId>
<name>Exercise for Intro</name>
<version>1.0.0</version>
<packaging>war</packaging>

<properties>
    <maven.compiler.source>1.8</maven.compiler.source>
    <maven.compiler.target>1.8</maven.compiler.target>
    <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding>
    <project.reporting.outputEncoding>UTF-8</project.reporting.outputEncoding>
    <failOnMissingWebXml>false</failOnMissingWebXml>

    <vaadin.version>14.0.0</vaadin.version>

    <drivers.downloader.phase>pre-integration-test</drivers.downloader.phase>
</properties>

<repositories>
    <repository>
        <id>central</id>
        <url>https://repo1.maven.org/maven2/</url>
        <snapshots><enabled>false</enabled></snapshots>
    </repository>
    <!-- Repository used by many Vaadin add-ons -->
    <repository>
         <id>Vaadin Directory</id>
         <url>https://maven.vaadin.com/vaadin-addons</url>
    </repository>
    <!-- Repository needed for prerelease versions of Vaadin -->
    <repository>
        <id>vaadin-prereleases</id>
        <url>https://maven.vaadin.com/vaadin-prereleases</url>
        <snapshots><enabled>false</enabled></snapshots>
    </repository>
    <!-- Repository needed for the snapshot versions of Vaadin -->
    <repository>
        <id>vaadin-snapshots</id>
        <url>https://oss.sonatype.org/content/repositories/vaadin-snapshots/</url>
        <releases><enabled>false</enabled></releases>
    </repository>
</repositories>

<pluginRepositories>
    <pluginRepository>
        <id>central</id>
        <url>https://repo1.maven.org/maven2/</url>
        <snapshots><enabled>false</enabled></snapshots>
    </pluginRepository>
    <!-- Repository needed for prerelease versions of Vaadin -->
    <pluginRepository>
        <id>vaadin-prereleases</id>
        <url>https://maven.vaadin.com/vaadin-prereleases</url>
        <snapshots><enabled>false</enabled></snapshots>
    </pluginRepository>
    <pluginRepository>
        <id>vaadin-snapshots</id>
        <url>https://oss.sonatype.org/content/repositories/vaadin-snapshots/</url>
        <releases><enabled>false</enabled></releases>
    </pluginRepository>
</pluginRepositories>

<dependencyManagement>
    <dependencies>
        <dependency>
            <groupId>com.vaadin</groupId>
            <artifactId>vaadin-bom</artifactId>
            <type>pom</type>
            <scope>import</scope>
            <version>${vaadin.version}</version>
        </dependency>
    </dependencies>
</dependencyManagement>

<dependencies>
    <dependency>
        <groupId>com.vaadin</groupId>
        <!-- Replace artifactId with vaadin-core to use only free components -->
        <artifactId>vaadin</artifactId>
        <exclusions>
            <!-- Webjars are only needed when running in Vaadin 13 compatibility mode -->
            <exclusion>
                <groupId>com.vaadin.webjar</groupId>
                <artifactId>*</artifactId>
            </exclusion>
            <exclusion>
                <groupId>org.webjars.bowergithub.insites</groupId>
                <artifactId>*</artifactId>
            </exclusion>
            <exclusion>
                <groupId>org.webjars.bowergithub.polymer</groupId>
                <artifactId>*</artifactId>
            </exclusion>
            <exclusion>
                <groupId>org.webjars.bowergithub.polymerelements</groupId>
                <ar

Tulio Garcia

@tulioag

@rajul3199 So, you are doing the training and having issues? Unfortunately there is not enough information here to find out what is going on, since there are lots of reasons for jetty failing to start, and it is a bit off topic for this channel. I encourage you to post a question in the forum at https://vaadin.com/forum/category/11562/02-miscellaneous with the complete source code of your project and everything that is printed on the screen from the moment you type mvn jetty:run to when the command exits.

Where communities thrive

People

Repo info

Activity