History and bookmark URLs

28 views

Skip to first unread message

cg85

unread,

Nov 2, 2018, 6:33:55 PM11/2/18

to intercooler-js

Hi there,

I'm very new to Intercooler.js and evaluating it for a web-app project. It looks really simple and at the moment looking at some cases where I haven't been able to find a clear answer (apologies if this has already been posted, couldn't find it anywhere).

In terms of the History example (e.g. http://intercoolerjs.org/examples/history_tab2.html) I can see that it correctly takes the user to the Tab 2, which is great. This means users can bookmark a URL and get the correct content.

However, when I click on Tab 1 for example, I can see in the Network tab (in Chrome's Dev Tools) that a full page is delivered in the Response instead of just the html segment that needs to be updated.

Following the documentation in the History page, I understand this is by design, right?

Does this mean that for any page that requires History support, the server would need to render the new full HTML page? Unsure if there is a better way, but wondering if there are other options.

Thanks!

cami...@gmail.com

unread,

Nov 3, 2018, 1:43:37 PM11/3/18

to intercooler-js

For everyone's benefit, I got a reply from Carson:

"Nope, I reworked that example to use full pages and a content selector so refreshing the page would work on the static site. If you are dynamically rendering the content you can look at the ic-request parameter to see if it is a partial tab request or a full page load and just render the appropriate content.

Hope that makes sense, and thanks for checking out intercooler!

Cheers,
Carson"

Thanks for clarifying, that makes sense, wasn't sure why the example was working like that. Cheers.