Manuel Carrasco Moñino

@knoobie thanks for reporting, we added a sentence in upgrading guide https://vaadin.com/docs/latest/upgrading/essential-steps

I think we should use the `state` serializable object in the `pushState` API, each time router calls to the method should pass the scroll position, then on `popState` it can...

At the same time consider why we still need this : https://github.com/vaadin/platform/blob/7add7a36e3f6b5126be9bff7e39d7793bbe1f214/vaadin-platform-test/src/main/java/com/vaadin/platform/test/CustomServletDeployer.java#L50

Consider an extra step for running vaadin-platform-tests in dev-mode, probaly only for snapshots in order not to penalize validation times for PRs

We are about to release vaadin-grid 2.0 polymer element, which is an entire rewrite of the component. Both the declarative and imperative API change, so the gwt library need to...

gwt-api will generate code to use it, but the api will change so we need to change the demos to adapt to the new grid api

Actually we have not thought on that. We have the mechanism to implement customised behaviours per element, but first we have to consider if there is interest on certain features....

This code work for me using GWT-2.8.0 and gwt-polymer-elements 1.7.0.0. Could you verify? otherwise, please share an example project manifesting the issue. ``` public class View4 extends Composite implements EntryPoint...

could you provide your entire ui.xml file ? seems like you need an auxiliary template for the data binding

Can you try 1.7.0.0-SNAPSHOT, this should be fixed.