Leif Åstrand

When this feature is implemented, it would be good to make a difference between caching a view instance forever and only preserving the old instance while the user navigates between...

We've implemented a Beacon handler as part of Collaboration Engine. It would be great if it could be moved over to the core framework instead.

Backporting seems to make sense from a technical point of view. The biggest concern is related to whether the effort would be worth it, but that's more up to @mstahv...

This sounds like you have the logic to show a login form based on the URL that is requested on the HTTP level, rather than also being based on Vaadin...

There is most likely a "login URL" managed by the Spring Security integration. In [our example](https://vaadin.com/blog/oauth-2-and-google-sign-in-for-a-vaadin-application) with Google login, it's `/oauth2/authorization/google` but I'm not directly familiar with what it would...

What can an attacker do with this debugging information that they couldn't also do by instead going to the network tab in the same browser console and picking out the...

I do agree that it would be good if the version number of Vaadin wouldn't be discoverable through the browser, but this is not as easy as it sounds for...

If all that matters is that information that is already present in the browser isn't displayed in the browser console, then replacing `console.log` is just as brilliant or as dumb...

@fabcan You can add the JavaScript snippet using the features described in https://vaadin.com/docs/v8/framework/articles/CustomizingTheStartupPageInAnApplication.html

Could also be noted that nowadays, you don't need to have a custom servlet for adding a custom session destroy listener. You can instead use a `VaadinServiceInitListener`. With Spring, you...