-
like the title said :)
-
after passing `pushState: false` to both `Backbone.history.start` and the `Router` instantiation this still doesn't play nicely with gh-pages. another issue is the absolute hrefs in `index.html` that …
-
When an handler as added to "\*" and then an handler is added to everything else, "\*" handlers have priority even I think it's not supposed to be so.
-
```
What steps will reproduce the problem?
1. historyInstance = new goog.history.Html5History();
2. historyInstance.setEnable(true);
3. historyInstance.setToken('e1'); historyInstance.setToken('e2');
…
-
```
What steps will reproduce the problem?
1. historyInstance = new goog.history.Html5History();
2. historyInstance.setEnable(true);
3. historyInstance.setToken('e1'); historyInstance.setToken('e2');
…
-
Although theoretically possible, we should demonstrate some sort of history support in one or all of the demos.
If we find this to be a royal pain, we should consider augmenting the plugin to support…
-
```
What steps will reproduce the problem?
1. historyInstance = new goog.history.Html5History();
2. historyInstance.setEnable(true);
3. historyInstance.setToken('e1'); historyInstance.setToken('e2');
…
-
How to reproduce:
1. Create a web-server and render wouter app with ``
2. On the client-side render your app wrapped in just ``
3. You will see the hydration warning.
Expected: when wouter runs…
-
https://medium.com/javascript-dots/how-to-use-history-api-on-javascript-401e4673cd5f
Started some work on this: https://github.com/jywarren/markdown-pages/pull/7
Questions:
* if people copy …
-
```
What steps will reproduce the problem?
1. historyInstance = new goog.history.Html5History();
2. historyInstance.setEnable(true);
3. historyInstance.setToken('e1'); historyInstance.setToken('e2');
…