Steps to reproduce
When I do a search, I get a list of hits. Clicking on a hit will take me to the new site. If I then click the BACK arrow, I’m back at the previous list of hits. But, if the new site had failed (usually due to my firewall) and a message appeared, "can’t reach site", I want to hit the back arrow and return to my hit list. Apparently, the list is lost and I’m 2 screens back. No other browser fails this way.
Comments and activity
- Microsoft Edge Team
Changed Assigned To to “Ali A.”
Bruce, thank you for filing this bug! I was hoping that you could provide more detail about how you were encountering this issue. First, would you be able to tell me the version of Windows and Edge you’re using? Can you also please confirm which search engine you experienced this issue with? Thanks!
Ali, thanks for the reply. Here’s the information:
Windows 10 Pro version 1607, 14393.693
I experience it with Google and Bing (among others).
Note: This is something that is 100 percent consistent. I can try it 100 times and it’s always the same. It’s very frustrating because sometimes I have spent minutes creating the perfect search string so the the Hit List is just want I want. I then slowly go through each item. When I accidentally hit an item that is blocked, I loose the whole list. ( If I leave the Hit List on its own tab, then I’m OK.) A year ago I stopped using Edge because of this anomaly.
Here’s a simulated procedure to see the problem.
- Launch EDGE
- In the search box type “headphones”
- You should get a typical hit listing.
- Type the following address in the address bar: "www.blivnard.com".
- You should now get a page not found error.
- Hit the back button to return to your hit list.
- Panic: What happened to the hit list? It’s gone.
Note: this scenario only happens on the EDGE browser !
- Microsoft Edge Team
Changed Status to “Confirmed”
Changed Assigned To from “Ali A.” to “Brandon M.”
Changed Status from “Confirmed” to “In code review”
Changed Status from “In code review” to “Fixed”
Thank you again for filing this bug Bruce! I’m happy to report that we’ve fixed the issue and it should be available in an upcoming Windows Insider build. Thanks!