I think I can make this work. I'm currently developing a solution, while addressing some other location bar parsing concerns.
The change should make it into the next GenomeBrowse release which is planned for later this week.
My tentative solution would allow the chromosome, start, and stop sections of the coordinate entry to be separated by any white space (such as the tabs in your example).
As long as all goes well, it should handle text formatted like any of the examples below:
1 10 20
1 10 - 20
1 : 10 - 20
chr1 10 20
chr1 - 10 20
chr1 - 10 : 20
This might mean that it can't handle something like:
chr 1 : 10 - 20
but, we will see.
Thanks for the suggested improvement.