Hello Kelvin,
Thank you for your report. I have examined it and found out that it works correctly. In the attached sample, I reproduced your scenario where the first button opens some link, and the second refreshes it.
It does not return the previous URL as you expected. And thus if you want to open the previous page, you should remember its URL elsewhere and then use it.
Thanks,
Vest
That problem is resolved when i downloaded and install the version 2.4 because before i was in version 2.3, but another problem is raised.
At the version 2.3 it worked fine but now it fires the an error. Look at the project attached.
This was at the first page of the project so we cant work or debug our application without resolving it. Please consider it with priority. Thanks in advance
Hello Kelvin,
Thank you for the application. I have examined it and found out that you call the "refresh" method in the form.onload event handler. When the event is raised, our controls are not fully initialized, and they might raise some exceptions.
To overcome the issue, you should use the ASPxGlobalEvents control in the following manner:
[ASPx]<dx:ASPxGlobalEvents ID="ASPxGlobalEvents1" runat="server"> <ClientSideEvents ControlsInitialized="function (s, e) { refresh(); }" /> </dx:ASPxGlobalEvents>
Thanks,
Vest
<dx:ASPxGlobalEvents ID="ASPxGlobalEvents1" runat="server">
<ClientSideEvents ControlsInitialized="function (s, e) { refresh(); }" />
</dx:ASPxGlobalEvents>
this is not the same as the onload of the body, because this is fired when you refresh some of the control too and i need the refresh() function to be executed only when page is loaded and not when i change or ad a control in it. I will try to make an example project but is very difficult for me. I hope you understand the case this way
Hello Kelvin,
Thank you for your patience. I have examined my solution and did not find errors on the client side. A page in the splitter is refreshed correctly, if you use the ASPxGlobalEvents control.
Of course, you can use the onload even as you did, but you have to wait a bit, before executing your code. Our controls need a time to end their initialization, and you cannot use them until this time.
The amount of time depends on page complicity and the browser speed. I think that 750 ms would be enough.
Thanks,
Vest
I don't like solutions with wait, but i found out that e.isCallback helped me because i wanted the function to execute only when it isn't a callback.
The problem with the RefreshContentUrl() of the splitter pane still exist and ONLY with IE.
Debugging your functions i have make 2 screen shots that shows why the behavior is different with IE.
NOTICE that the element.src is different than contentWindow.location.
I dont know if this is a bug but the problem persist only with IE and not with the other browsers.
Its very difficult for me to create a sample project. Thanks in advance
Kelvin,
Thank you for screenshots. However, I am afraid that I cannot reproduce the issue using them. In fact, IE has some specific places where we wrap our code in try...catch blocks.
Since, the exception is handled, and you do not see error on the screen, I do not think that this is a bug.
But, we are glad to process the issue, if there is a chance of getting the same result on our side. I apologize that your application is complex, but perhaps it is possible to create a small sample which throws the exception?
Thanks,
Vest
Finally i have the sample project for you.
The main page has 2 panes with splitter. once i click the button "open refresh" it opens in the second pane the refresh.aspx. When you click on the button inside the refresh.aspx the pane is redirected to WebForm2.aspx. After that when i click on the button "open refresh" again in IE it just refreshes the pane2 so the result is that in the pane 2 i have WebForm2.aspx again.
What i want is that the "open refresh" button opens in pane2 the refresh.aspx always. This works very fine in chrome or firefox but not in IE.
Waiting for your response. Thanks in advance
Hello Kelvin,
Yes, I see the difference between browsers. And I decided to forward the report to our developers, so they can examine it.
In the past we had several reports regarding refreshing the splitter content, and our developers successfully fixed them.
Please excuse me for a possible delay. We hope to respond soon.
Thanks,
Vest
Hello Kelvin,
Thank you for your patience. Our developers have examined the report and admitted that it is a bug. I have converted the question report to a bug, so they can fix it.
A possible fix will be complex, and I cannot tell you when it will be ready.
Please excuse us for the delay.
Thanks,
Vest
Is your intention to post an answer to your own question?
- If so, then proceed.
- If you simply wanted to post additional information, ask for further clarification, or to just say "Thanks!", please click Leave a Comment.
- If you wish to edit your original question, please use the Edit button in the Toolbox at the top right corner of that entry.