search

rhomobile / rhoelements-issues

Issues area for RhoElements
0 stars 0 forks source link

Page load timeout #65

Closed heyheysay closed 10 years ago

heyheysay commented 10 years ago

Customer is being redirected to the badlink page. It looks like the page load is timing out. This is an issue with the amount of time a page is taking to load and not a network connectivity. WM 6.5.3 mc9290 Rho 4.0

Three questions.
Can the page load timeout value be changed?
What is the current page load timeout value? What event will cause the badlink page to be displayed?

heyheysay commented 10 years ago

Another item on this is to have the different timeouts/ reason why you got directed to the badlink page to show up in the Rholog.

heyheysay commented 10 years ago

We are seeing the time out in only a few seconds.

darryncampbell commented 10 years ago

Hi Glenn, what do you mean by page load timeout? The Nav Timeout is the time for the server to respond (default 45 seconds), we don't have a timeout for the actual time taken to render the page.... is that what is being asked for?

darryncampbell commented 10 years ago

If it is going to the badlink page after just a few seconds it probably means the device had some problem like couldn't resolve the domain name or was configured incorrectly for a proxy (that sort of problem)... the reason is available as part of the URL when you are directed to the badlink page (see the code of the default page for example of how to use this)

heyheysay commented 10 years ago

It looks like our Webkit with the Shared Runtime is having JS/DOM timing issues. These issues are only appearing with the Webkit and in fact go away when Weinre is used with the Webkit. The leads me to believe that I have a JS code conflict or I’m going after the part of the DOM that is not created/completed yet.

When we see this error the page starts to load, but then is redirected to the badlink page after only a few seconds. If we reduce the number of items in the drop down list from 30 to say 5 the issue goes away. Thus the link to timing problem.

Questions; • We are currently using the onload event to define when the DOM is done loading. Is this what we should be using or is there something better? o
• Does anyone know of a way to trace DOM and JS interaction? • Any other tracing that I can do to see what state the DOM is in when the JS executes?

darryncampbell commented 10 years ago

It shouldn't be going to the bad link page part way through loading the page, regardless of how you have defined your JS / DOM interaction. Can you share the page?

darryncampbell commented 10 years ago

Hi Glenn, Maybe we could continue this via email? Or a call... I think we need to talk through the problem.