I'm wondering about something I observe, but don't know enough or what I might do about it.
First, an observation:
If a user navigates to Page A for the first time during a session, it takes, say, 4 seconds to load the page. User submits record, navigates to previous page (a menu of sorts), then back to Page A again. This time and all subsequent times, it takes just 3 seconds to load the page.
With this observation (roughly described) in hand, let's move to a different page/component and the current problem:
User pokes button that loads a 30-row updateable grid in an AJAX window. Last 5 rows of the grid don't behave well when javascript methods and functions are called in those rows. Close the AJAX window, call it again with another 30 rows (different records mind you) and the last 5 rows behave well with javascript actions in the rows. This part that I'm describing here only occurs on the iPad, occurs a little unpredictably, but more often than not, and is not an issue on wired machines. Yes, iPad connectivity is terrific -- rule that out please.
So, with this latest problem that I cannot seem to resolve, and these observations, I'm wondering if there's some kind of javascript caching going on with our pages and/or AJAX windows. And, if there is, is there a way I can "push" the javascript out there before or during the first load of the page/component to help alleviate some of this behavior?
I don't know if this sounds "out there" or not but this "last 5 rows" problem just doesn't seem to have a solution so I'm stretching a little further than usual to find some way to manage it.
First, an observation:
If a user navigates to Page A for the first time during a session, it takes, say, 4 seconds to load the page. User submits record, navigates to previous page (a menu of sorts), then back to Page A again. This time and all subsequent times, it takes just 3 seconds to load the page.
With this observation (roughly described) in hand, let's move to a different page/component and the current problem:
User pokes button that loads a 30-row updateable grid in an AJAX window. Last 5 rows of the grid don't behave well when javascript methods and functions are called in those rows. Close the AJAX window, call it again with another 30 rows (different records mind you) and the last 5 rows behave well with javascript actions in the rows. This part that I'm describing here only occurs on the iPad, occurs a little unpredictably, but more often than not, and is not an issue on wired machines. Yes, iPad connectivity is terrific -- rule that out please.
So, with this latest problem that I cannot seem to resolve, and these observations, I'm wondering if there's some kind of javascript caching going on with our pages and/or AJAX windows. And, if there is, is there a way I can "push" the javascript out there before or during the first load of the page/component to help alleviate some of this behavior?
I don't know if this sounds "out there" or not but this "last 5 rows" problem just doesn't seem to have a solution so I'm stretching a little further than usual to find some way to manage it.
Comment