Forum Discussion
Policy needed: "Go to an intranet site for a one-word entry in the Address bar"
Thank you, ToMMeR, stesch79 and paf_skov for your feedback. I can appreciate those circumstances and your request.
We will look into adding a policy to make single-word queries navigate and I'll follow up on this thread with an update as soon as I have one.
Thanks again for giving us this important feedback and for describing your specific scenarios! It helps!Jared
Update: Dev channel build 79.0.309.5 has been released. It should contain support of dots for single-word direct navigation if the policy is enabled.
ToMMeR, please test this out and let us know how it works for you.
Thank you,
Jared
JaredB81 in version 79.0.309.5 the logic behind when to search and when to visit a website still seems strange and in a way that would lead to quite a lot of search engine searches where a internal website was what was intended.
Take "test.vejle.intern" as an example which could be an internal hostname.
- "test" correctly tries to go to the hostname.
- "test." tries to do a search engine search (why?).
- "test.v" still tries to do a search engine search.
- "test.ve" correctly tries to go to the hostname.
- "test.vej" tries to do a search engine search.
- "test.vejl" still tries to do a search engine search.
- "test.vejle" still tries to do a search engine search.
- "test.vejle." still tries to do a search engine search.
- "test.vejle.i" still tries to do a search engine search.
- "test.vejle.in" correctly tries to go to the hostname.
- "test.vejle.int" correctly tries to go to the hostname.
- "test.vejle.inte" tries to do a search engine search.
- "test.vejle.inter" tries to do a search engine search.
- "test.vejle.intern" tries to do a search engine search.
I do not understand why the logic behind it has to be this complex.
When the group policy is set, why don't you just treat anything a hostname until a character that is not valid in a URL is typed (like for example a space)?
JaredB81 I can confirm that "." (dot) now works as expected.
It correctly keeps to a hostname when you do dots and dashes and doesn't do a search engine search until you type a space.
Thank you for the fix!
Any status on the ability to fail back to search after a few seconds if the hostname is not resolved?
I can see that build 79 is heading to GA, so I am wondering how long we have to wait for this until we can deploy a GA Edge version to our users?ToMMeR, the "dot" fix should now be available in the latest Dev build (79.0.309.11). Please give it a try and let us know how it works for you.
ToMMeR, Aaron Roma, Omega47, AngelPRU, paf_skov and stesch79, we have determined a feasible and safe approach to enable the search fallback behavior. Development is underway and once the solution has been implemented, I will update this thread so we can get your feedback on the search fallback behavior.
On behalf of the Microsoft Edge team, thank you again for testing and for your valuable feedback! We appreciate it!
Jared
ToMMeR, thank you for your feedback.
Your testing did not match my expectation and after looking into it, it turns out the fix didn't make it into the 79.0.309.5 Dev channel build. Our team has now checked in the fix to make sure it is in the next Dev channel release. I'll update this thread once that has taken place and then I'll kindly request you run these test cases again.
Thank you for your patience and I apologize about the confusion.Jared