iSeller Commerce
iSeller POS Retail
iSeller POS F&B
iSeller POS Express
Crosslight
WebUI
ClientUI
What's New
Download Trial
Web Solution
Mobile Solution
Enterprise Solution
Custom Development
Blog
Community
Latest Development Blogs
ForumPostTopic
Browse By Tag
Hi,
We have recently up graded to the latest version of the WebDesktop.dll (v3_0_7200). Since we did this we are getting a javascript error on the closing on one of our WebDialogBoxes. This only happens when we use a cancel button to close the WebDialogBox. If I roll the WebDesktop.dll (v2_5_2007) back to the previous version the javascript exception doesnt materialise. We use the same WebDialogBox from multiple parts of the web application to host pages that also have cancel buttons and the error only appears in this one place. The error that is happening is a "Permission Denied" error on the code "event.cancelBubble =true;" in the ISRes.axd file. Any help in resolving this issue would be much appreciated.
Regards,
Dermot
Hi Dermot,
I am having a problem to replicate the issue of yours. Here, I attached you a simple sample of WebDialogBox which has a cancel button in it. Could you kindly try to run them and see if the error is persisted in your end? However, for a better result, before you try the sample, perhaps you could update all the hotfix to the latest one from your UpdateManager.
Currently, I am using WebDesktop v3.0.7200.309. Could you provide me with your WebDesktop's build version please?
Thank you and have a nice day.
Best Regards,
Andi Santoso
Hi Andi,
Thanks for you quick reply. I am currently using v3.0.7200.308. I donwloaded the latest host fix but it did not solve my issue. I have expanded the example you gave me to replicate the issue. In doing this what I have found is that the use of a webtab is what causes the error. In the example I have attached we use the webdesktop that has a WebDialogBox using Iframe. The ContentUrl points to a page that has a WebTab also using IFrame. The first tab hosts an aspx page that has a cancel button on it. If you click the cancel button you will be able to replicate the issue we have. When I bypassed the webtab page through the webdialogbox ContentUrl, the error did not materialise. But we need the webtab for our application so this is not a solution. Hope this information helps in solving the issue.
Thank you for your detail information. I am able to replicate the issue right now. After I break them down, I noticed that IntegratedToDesktopManager is the main cause of this. I have tried to re-run your project with IntegratedToDesktopManager in WebDialogBox1 in your "Cancel_DialogBox.aspx" file removed, and the error is not persisted.
I have forwarded this to our developer team. In a mean while, perhaps, instead of set the style to be integrated, we can re-style them manually. I will inform you as soon as possible when I heard news from our developer team. I hope it helps.
Thanks for your reply. I have looked into the setting IntegratedToDesktopManager to false. This does solve the error but by making these changes we break some other functionality we have written. I call a single WebDialogBox from the multiple places through out my application. I use an Iframe to load in different pages. When I set the IntegratedToDesktopManager to false, the previously loaded page appears before the new page is loaded in. This does not look good. This does not happen when IntegratedToDesktopManager is set to true.
I will hold off in making the change you recommended as the issue I have mentioned above will be considered greater in serverity than the initial issue.
Please let me know once a timeline is available from your developers to fix the inital bug I logged.
Thanks again,
Sure, I will make sure to let you know as soon as possible when I get news from our Developer team. Thank you.
Dear Dermot,
First of all, deeply apologize for a very late respond. I just wanted to let you know that the issue has been fixed.
I have attached you the nightly build hotfix of WebDesktop. Please kindly apply this hotfix to your project. Also noted that this is a nightly build, any feedback regarding this hotfix would be really appreciated.
or
Choose this if you're already a member of Intersoft Community Forum. You can link your OpenID account to your existing Intersoft Social ID.
Choose this if you don't have an Intersoft account yet. Your authenticated OpenID will be automatically linked to your new Intersoft account.
Enter your Wordpress Blogname