RootsChat.Com
General => Technical Help => Topic started by: aghadowey on Tuesday 12 December 17 11:10 GMT (UK)
-
At least I think it's probably some setting I've selected by mistake?
Using Microsoft Edge as browser (with newish Windows 10 Home computer). Yesterday when waiting for a site to come up I see 'waiting for response from..' on tab (can't remember seeing this before). However, the real problem is when I'm on some sites (which I've used previously), view a record then click the back button* to return to results on previous page- then I get the following-
'This page was just here a second ago. Try refreshing. You may need to look through this site again... Try this. Refresh'
So, I click 'refresh' and get NOTHING happening.
So, I click my own refresh button and get this-
'Resubmit form. To refresh this page your browser needs to repeat any actions you've already taken. For example, if you've already entered into into a form, your info will be resubmitted to the site' with 2 button choices- Retry of Cancel
So far using my refresh button seems to work but really slows down searching.
Any ideas how I can fix this?
* note- using PRONI Will Extracts search page today I've discovered I have no problem- unless I click on an image (which comes up in another window) then get the above problem trying to go back in original search page
-
Hi
I cant help with your problem, but just to say there was a big update recently that my computer did (I use Microsoft edge, Windows 10 etc same as you) and since then I have had that "Waiting for response from...." in the tab, that I didn't have before. So I put that down to changes made in the update. But every else is working OK for me, apart from when I turn it off, it keeps saying there is an app still open (which there isn't), it didn't do that before. But I can click on "shut down anyway" so it isn't really an issue.
Hope you get sorted.
-
Good to know that the 'waiting for response' thing has not just appeared in my computer. Haven't any problem closing down at least :)
-
You're not alone. I get it on FreeBMD but not anything else.
-
You're not alone. I get it on FreeBMD but not anything else.
Interesting, I'm getting it on FreeBMD also. So looks like I didn't cause the problem after all?
-
I switched from Chrome to Edge a couple of weeks ago because I kept getting a message saying "web page didn't shut down correctly". So looks like browser issues with W10.
-
I get something similar with GRO site sometimes.
My computer can be a bit slow after an update. Mine is 2 years old and came complete with Windows 10.
-
I often get a message "We're working on it" when I'm doing tasks with Windows 10 and I use Firefox Mozilla (not their new update which I don't like!)
-
i'm getting the waiting for a response message and also it was here a few seconds ago and that's since the last update.
-
I'm getting "waiting for response" on a site I used during last 2 days. Hadn't noticed it before.
There's also a minor change in the method of adding & naming new folders for my Favourites list. I added something today, not realising the alteration, then had to delete the new folder + contents before adding it again the correct way.
-
This is a problem that many users of Windows 10 Microsoft Edge browser have been experiencing since a recent Windows Update.
I've seen this problem on many family history web sites (Deceased Online, FreeBMD, GRO Online Index, PRONI Wills, etc.), and it's a real pain to keep having to use the F5 button and resubmit the page request dozens (if not hundreds) of times a day, when you're doing these searches.
If you were to complain and submit information to the Microsoft Answers (on their Microsoft Edge / All other issues / Windows 10) problem solving forum, it may spur them to put a bit more effort into this.
https://answers.microsoft.com/en-us/edge/forum/edge_other-edge_win10/i-have-just-started-having-a-problem-with-edge-and/d8b7070a-9aae-437d-a028-8923a3df211d?messageId=6842b7bb-f347-4053-a44d-ac791549bc9c
Once you've complained, I'd switch to Internet Explorer, Chrome or Firefox browsers, which don't have this problem.