Why does the url keep refreshing when I am not touching it?
I typed in the website (www.n2yo.com) and pressed return to open it. Unfortunately it just keeps acting as if it is refreshing and not opening the webpage. Ie the image to the left of the url keeps flashing in alternation with a square like shape, and the progress circle and line at the top just keeps flashing and resetting.
It worked fine yesterday. Certain parts of the website worked fine earlier today also. But now every variation of a page within that site seems to be doing the same thing.
Thoughts? Guidance?
選ばれた解決策
I see the same when visiting that website with Firefox and Google Chrome.
I looks that some JavaScript that runs on that website is broken as I get a page when I disable JavaScript.
The web console shows a lot of error messages like these:
An unbalanced tree was written using document.write() causing data from the network to be reparsed. For more information https://developer.mozilla.org/en/Optimizing_Your_Pages_for_Speculative_Parsing @ http://www.n2yo.com/:12
You can contact that website to inform them about this issue.
この回答をすべて読む 👍 1すべての返信 (4)
First, update Firefox to 17.0.1 Update Firefox to the latest release
Then, update your plugins. https://www.mozilla.org/plugincheck/
Finally, read Websites look wrong or appear differently than they should
選ばれた解決策
I see the same when visiting that website with Firefox and Google Chrome.
I looks that some JavaScript that runs on that website is broken as I get a page when I disable JavaScript.
The web console shows a lot of error messages like these:
An unbalanced tree was written using document.write() causing data from the network to be reparsed. For more information https://developer.mozilla.org/en/Optimizing_Your_Pages_for_Speculative_Parsing @ http://www.n2yo.com/:12
You can contact that website to inform them about this issue.
For some reason it seems to work now. Seems like the problem is either with the site or between. Thanks guys.
この投稿は RadioRaheem により に変更されました
Yes, the site works for me now as well, so it appears that they have fixed this problem.