Vaadin 7.3.0 and PopupView

Vaadin 6 / 7 / 8
1

Hi guys.

Has something changed with the order of events fired with regards to PopupViews being shown/hidden in 7.3.0 (was previously on 7.1.5).

My Situation: I have a form with multiple rows, and each row has its own PopupView. The content for each PopupView is a shared instance (a panel with 3 buttons that are enabled/disabled according to the row when the PopupView is triggered). The reason I use shared content is that I may have 1000+ rows on this form, and it will save quite a bit of memory.

scenario 1) If I open a PopupView on row 1, close it properly (by clicking outside it), then open a PopupView on row 2 - everything is OK.
scenario 2) If I open a PopupView on row 1, then click on the PopupView on row 2 (whilst PopupView for row 1 is still open), I get exceptions thrown from Vaadin about my popup content already being attached to a parent.

Inserting some trace, I can see in scenario 2 that the PopupView for row 1 is not being closed down properly by Vaadin before the PopopView for row 2 is made visible. If I apply the trace to Vaadin 7.1.5, the first PopupView is closed correctly before the seconf PopupView is opened.

Is this a bug? Chances of it being fixed?

Cheers,
Lee.

2

Anybody have time to answer? Event order has definitely changed…

3

Hi Lee,

I might suspect this is again something related to the fact that overlay elements are now animatable with CSS when they are brought into and out of view.

Do you get the exception in the server or in the client? Trying to pinpoint the reason (without actually testing myself).

4

I confirm the issue is caused by animations, because if I disable them ($v-animations-enabled: false;) everything is OK again.

Whether its server or client side, unknown. How could I tell? I get an error in the server log if thats any help :wink:

5

Hi Jouni. Any update on this? Or should I raise a dev ticket?? Basically, animations are chaning the order of popup view events and it breaks our code.