Improve external Chrome opening sequence

[anssit]

Automatically opening the external Chrome editor takes users by surprise initially. There is considerable lag in the opening sequence. Figure out a way to improve the sequence to be less surprising and less laggy.

Steps to reproduce

1) Configure to use the external Chrome editor 2) Create or open a design

Actual behavior

1) Browser tab is opened, moving the browser to topmost window 2) The design file source editor is opened in IDE but with considerable lag

Expected behavior

UX test feedback suggested that users either would like to launch the editor manually, or at least the see the source mode editor open immediately, and only then the browser tab. This would be more natural to the IDE users (to see the file open in the IDE).

All UX test subjects thought there's too much lag in the opening sequence.

IDE, Designer and OS version

Designer with external Chrome editor feature, any OS, both IDEs.

[vesanieminen]

Sometimes I just want to quickly open a template, change some non-Designer related things like imports and then I wouldn’t like to wait a few seconds for a Chrome tab to forcefully open.

To support that I think it would make sense to add a checkbox to the Designer preferences for not automatically open design in the browser.

Currently when editing multiple files like that I either will not use my IDE (not good) or have the urge to uninstall Designer completely (even worse).

[Peppe]

I would like to see next it very easy to change the defaults next to the buttons where you change the mode manually. eg. [open in Designer] [change default]

I don't know exactly what "change default" would say or what kind of control it would be. When you manually are changing the mode, then maybe you'd want it to always behave the other way. It should be easy to go to both directions.

[stale[bot]]

Hello there!

It looks like this issue hasn't progressed lately. There are so many issues that we just can't deal them all within a reasonable timeframe.

There are a few things you could help to get things rolling on this issue (this is an automated message, so expect that some of these are already in use):

• Check if the issue is still valid for the latest version. There are many duplicates in our issue tracker, so it is possible that the issue is already tackled.
• Provide more details how to reproduce the issue.
• Explain why it is important to get this issue fixed and politely draw others attention to it e.g. via the forum or social media.
• Add a reduced test case about the issue, so it is easier for somebody to start working on a solution.
• If the issue is clearly a bug, use the Warranty in your Vaadin subscription to raise its priority.

Thanks again for your contributions! Even though we haven't been able to get this issue fixed, we hope you to report your findings and enhancement ideas in the future too!