router
router copied to clipboard
Don't include fragment identifier when matching.
I ran into problems with fragment ids causing URLs not to match and it seemed odd to match on them, given the the server doesn't normally see them.
@jancona can you provide some more context on the problems you were running into? go-humble/router is designed to fallback to using fragment ids whenever history.pushState
is not supported. I'm hesitant to accept this change without understanding why it is necessary and how it might affect behavior in older browsers that do not support history.pushState
.