You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If a link does not starts with the baseUrl, it should be ignored by the onclick handler and should continue to have their native behavior.
Any link whose pathname contains (not starts-with) the base url will fail to be ignored by the onClick handler. As a result, links that should actually go to a different page are triggering page.js routes instead.
For example, if my app has a base url of "/b", the link below should be ignored by the onClick handler, and the native behavior (opening that url) should be preserved:
<ahref="/a/b/c.html">Some File</a>
But instead, the onclick handler prevents the default action and calls page.show('/a/b/c.html')
I'll submit a pull request...
The text was updated successfully, but these errors were encountered:
Wow, I completely disagree with this. At the very least, you should have the option to not use it that way. With this current setup, if someone decides to change the base, you have to go through your entire codebase to change it. That's nasty and super not cool.
If a link does not starts with the baseUrl, it should be ignored by the onclick handler and should continue to have their native behavior.
Any link whose pathname contains (not starts-with) the base url will fail to be ignored by the onClick handler. As a result, links that should actually go to a different page are triggering page.js routes instead.
For example, if my app has a base url of "/b", the link below should be ignored by the onClick handler, and the native behavior (opening that url) should be preserved:
But instead, the onclick handler prevents the default action and calls
page.show('/a/b/c.html')
I'll submit a pull request...
The text was updated successfully, but these errors were encountered: