There seems to be some issues with an Ajaxified RadGrid when using WebKit Browsers like Safari or Chrome. Both seem to issue back to back requests (and way too many responses); these are not present in IE or Firefox. This is causing an issue due to the fact the loading panel is immediately turned off after the first response, while second request continues to process with no panel (which allow our users to access to areas they should not have while data is being processed). We're currently using Q2-2009 controls in the affected project.
The sample below is setup such that a user may end their filter entry with ENTER, which kicks off an onclick event for a hidden button. This is done so a known control causes the request and can be identified on response. Attempting to decipher which internal RadGrid element caused the response is a bit cumbersome. You will notice that IE and Firefox only deal with the hidden button, while Chrome and Safari seem to push the RadGrid Filter Textbox into the mix. Is there any work around for these browsers? Is this a known issue?
SafariAjaxRequestProblems.zip
*** Please note this issue is not isolated to the RadGrid (we have seen it happen it other places), but this example was easy to pull out of our main project. I'm sure if we can solve this issue, we will be able to remedy it in other areas as well. I've already generated a much simpler sample and issued it in the radinput forum as this seems to be the direct source of the problem.
The sample below is setup such that a user may end their filter entry with ENTER, which kicks off an onclick event for a hidden button. This is done so a known control causes the request and can be identified on response. Attempting to decipher which internal RadGrid element caused the response is a bit cumbersome. You will notice that IE and Firefox only deal with the hidden button, while Chrome and Safari seem to push the RadGrid Filter Textbox into the mix. Is there any work around for these browsers? Is this a known issue?
SafariAjaxRequestProblems.zip
*** Please note this issue is not isolated to the RadGrid (we have seen it happen it other places), but this example was easy to pull out of our main project. I'm sure if we can solve this issue, we will be able to remedy it in other areas as well. I've already generated a much simpler sample and issued it in the radinput forum as this seems to be the direct source of the problem.