I've gone through all the components and collected media queries we use.

I tried to apply the "Using Polymer Elements in Angular CLI Webpack" tuto,
on 1.0.0-beta.11-webpack.8 without success on Firefox.

But the trick is here : angular/angular-cli#1747
The polyfill
<script src="bower_components/webcomponentsjs/webcomponents-lite.min.js"></script>
has to be call in global in angular-cli.json

Description

Currently <vaadin-date-picker> isn't aligned in keyboard a11y with native input[type="date"]. Focusing the date changes the value:

Jouni Koivuviita [1 hour ago]
But in combo 

Would be nice if we can give the more detailed reason of failure, not just “server unavailable”. Might be good to show the detailed information in a tooltip or on click.

Suggestion done during the UX testing

The example page should list the unicode value of each icon in the font.

Here’s an example from the old marketing website:

Demos doesn't work on 2.0-preview

There are few things to make them work again:

• Change <style is="custom-style"> to <custom-style><style is="custom-style"></style></custom-style> (Hybrid syntax valid for 2.0 and 1.0)
• Change <template is="dom-bind"> to <dom-bind><template is="dom-bind"></template></dom-bind> (Hybrid syntax valid for 2.0 and 1.0)
• Import `<link rel="i

I was trying to take into use in a pie chart, but I wasn't able to put values in a format that it accepts. For a pie chart, you want to specify for each slice y (which is the size of the slice) and name (which is the name of the slice).

How ever i tried to give in the slices as objects with y and name, I just got a blank graph. I couldn't see over at https://charts-demo.ap

The README claims that to see a full-blown example of variable change triggering re-execution of the query one should look at the third example. The third example is no different from the second example and does not use bound variables in it's query.

https://vaadin.com/components/vaadin-context-menu/html-examples/context-menu-items-demos demonstrates nested menu items API.

https://vaadin.com/components/vaadin-context-menu/html-examples/context-menu-basic-demos#defining-content-with-polymer-templates does not make it clear whether a nested menu is also possible via HTML templates?

The change landed in #107 was targeting the form-layout placed in the element with flex-direction: column, but it was actually breaking change from the point of view of the users who try to center form-layout in the container setting flex-direction: row

This should have been released as 3.0.0 but we didn't do that. The proper way of handling this would be reverting change, releasing 2.1.3

Issues

• Fix import not working when using Webpack #15

Code

• Use LitElement instead of Polymer
• Use open-wc/testing instead of WCT

Development

• Improve serve (use Parcel bundler)
• Move style to a stylesheet file
• Add eslint config

Release / CI

• Improve CI release config
• Include a bundled release

It is very common that people want to get rid of the padding in dialog. For example if you want to make a header for the component that goes edge to edge, you would have to remove the padding. Add a theme variant where it is removed from the overlay. Here's how you do it manually.

<dom-module id="custom-dialog" theme-for="vaadin-dialog-overlay">
  <template>
    <style>
      :host([the