Strange behaviour in local and live environment

[Martin Sato]

Hi,

  I have a dialog with declaration as follows:

<SfDialog @ref="dlg" pos Width="50%" Target="#uppertarget"

      ID="dialog"     ShowCloseIcon="true" IsModal="true" Visible="false">

 When shown, I have a second dialog with declaration as follows:

<SfDialog @ref="dlg" pos Width="80%" Target="#dialog.e-dialog"

          Visible="false">

Both, I am using their ref variable to call as follows:

await dlg.Show();

The strange behavour in local/dev environment, the second dialog pop ups on top of the first one, but in the hosted environment, it is still showing at the back of the first dialog, please see image 

Local Image

Live Image

Thanks.

[Indrajith Srinivasan]

Hi Martin, 

 

Greetings from Syncfusion support, 

 

We have validated your reported query, using the shared information. With the shared code blocks @ref component instance is used for two different SfDialogs in the page, which is not recommended way. We suspect the reported issue occurs, due to components common instance for Show() method call. We suggest you to maintain, difference component reference (@ref) for calling the components Show() method.  

 

Can you try the above suggestion and let us know if you still face any difficulties ? 

 

In the mean-while, can you please share us your live accessible environment to validate the reported issue from our end ? 

 

Regards, 

Indrajith 

[Martin Sato]

Hi Martin, 

 

Greetings from Syncfusion support, 

 

We have validated your reported query, using the shared information. With the shared code blocks @ref component instance is used for two different SfDialogs in the page, which is not recommended way. We suspect the reported issue occurs, due to components common instance for Show() method call. We suggest you to maintain, difference component reference (@ref) for calling the components Show() method.  

 

Can you try the above suggestion and let us know if you still face any difficulties ? 

 

In the mean-while, can you please share us your live accessible environment to validate the reported issue from our end ? 

 

Regards, 

Indrajith 

it's gone now, maybe because of the same name of the sfdialog, although they reside on a different component, but changing the name resolved the issue. Thank y ou.

[Revanth Krishnan]

Hi Martin, 

 

Thanks for the update. 

 

We are glad that the reported issue is resolved on your end. Please let us know if you need further assistance. 

 

Regards, 

Revanth