hash from an anchor is passed directly to root.querySelector with our regard for what might be contained in the hash.

Hash-routing libraries store the route in the hash. For example an anchor tag may have #!/foo/bar as the value for the href.

Passing this value to root.querySelector causes an error, for example SyntaxError: The string did not match the expected pattern. in safari or Uncaught DOMException: Document.querySelector: '#!/foo' is not a valid selector in FIrefox.

This could be solved in two ways:

1. a simple try/catch
2. further expand the regex to allow for detecting a valid query selector string before passing it to querySelector

@wessberg if you have a preference between the two approaches (or have an alternative suggestion) I am happy to open a PR that fixes the bad assumption around what can live in a hash.