URL Address bar interpretation of incomplete URL address

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Is there any way to control the way incomplete URL addresses are interpreted.
Since we don't have to type "http://" anymore I would like to add a futher
shortcut to the address bar.

This would be the follows:

1. Intepret all spaces between words or letters entered by the user to mean
a single dash "-".
2. Assume the website is a ".com" TLD if one is not specified.

This would allow me to type "penny arcade" and it would translate to
"http:\\www.penny-arcade.com".
Another example would be "Wells Fargo" that would go to
"http:\\www.wells-fargo.com" (which does go to the real Wells Fargo Bank
site).

When browsing first started out you had to type "http://www" infront
of everything. Then it seemed like browsers got smarter and allowed
people to save time by just typing "mozilla.com" instead of
"http://www.mozilla.com".
Now that we have many sites with dashes, it just seems like there should be
a way
to change the browser to make assumptions about incomplete URLs without
resorting to a search engine query (which many browsers are set to do,
mainly to Google, Yahoo and MSN). It is a shame that dashes are sort of
relagated to
the domain name backwater when it could be made a more richer environment
without having a lot of setup work. I would love to type in "This Cool
Site" and
have it go to "http:\\www.this-cool-site.com". It would seem to balance
things out
a bit better than "www.thiscoolsite.com" and not lead to constant fighting
to get a short domain name with words all crushed together. Plus there are
already cool sites out there (Penny Arcade is a favorite) that have a dash or
two in the name.

Anyway, thanks in advance and look forward to the replies.

Regards,
Sam G.
 
Why don't you use favorites/bookmarks/links? It's even simpler :)
One problem with spaces being interpereted as dashes is filenames. Spaces
are characters too and are interpreted as %20 I think. That would make the
adress parser more complex as it would have to distinguish when it can
interpret spaces as real spaces in filenames and substitute %20 and when it
has to substitute dash.
Making .com a default extension would make parser even more complex. And
what about those who use adress bar as a search bar (like me)?
I'm not saying it can't be done it's just not worth doing it, IMHO...
 
Back
Top