Leif Åstrand

What would this feature help you achieve? Could there be another way of achieving that without relying on deprecated features?

The correct place to address this would probably be in https://github.com/vaadin/flow/blob/e973f16fe406fde24b0a6d987c5b9a9d9a2d5784/flow-plugins/flow-maven-plugin/src/main/java/com/vaadin/flow/plugin/maven/FlowModeAbstractMojo.java#L245-L248

For reference, this is the discussion that lead to including this feature in Spring Boot. https://github.com/spring-projects/spring-boot/issues/2224 To me, the key point is really this comment: > Usecase where I see...

...and here's a discussion related to why the Maven maintainers think that the system scope should be deprecated: https://issues.apache.org/jira/browse/MNG-6523 My interpretation is that Maven has this feature for other purposes...

State is so 2020. I would suggest a signal instead.

I don't see how we could have anything based on a timeout for a case like this. It's not really acceptable that the UI remains functional only if the server...

It's very unexpected that a slow download response would cause a clean shutdown of the UI and it becomes even more difficult for the developer to understand what goes on...

The problem is that not all legacy download links have the `download` attribute set which means that we cause regressions for existing applications where it previously wasn't an issue to...

Related concept outside Grid: https://github.com/Legioth/repeater/blob/master/src/main/java/org/github/legioth/repeater/Repeater.java#L256

I've created an actual running example based on my idea with the Beacon API. See https://vaadin.com/forum/thread/17523194/18399446 for more details.