Xpages ajax request impacts context history

Question

I have a simple Xpage (page1.xsp) opened from view.xsp page. It contains the following elements
1) Back button written in SSJS

context.redirectToPreviousPage()

2) CSJS script that does ajax get every x minutes

dojo.xhr.get({
    url:"page2.xsp?param1=value1",
    handleAs:"text"  
});

My probem is that after several ajax requests my Back button goes to page2.xsp (ajax get page) instead of view.xsp.

How can I make it go back to view.xsp page?

score 1 · Answer 1 · answered Jan 28 '16 at 08:44

1

Not an answer, but when I've had a "form" accessed from multiple "views" and want to know which one to go back to, I store it in sessionScope when opening the "form" and then just access that sessionScope variable.

answered Jan 28 '16 at 08:44

Paul Stephen Withers

15,699
1
15
33

Paul, I've considered this option. But you know - many start views, many tabs open and you got a mess :) – dj_universe Jan 28 '16 at 08:55
I agree, it depends on application usage model – Paul Stephen Withers Jan 28 '16 at 09:14

score 1 · Accepted Answer · answered Feb 02 '16 at 16:45

The back button and XHR behave very different in different browsers, so I wouldn't rely on it. Relying on a session variable is - as you pointed out - could become messy. So this is what I would do: store the page to return to in a session variable (yes), but only to hand it over to the page the very moment.

Pack it into a script tag using var whereToGoBackTo = '${sessionScope.theLastPageCameFrom}' and store it client side. Since it is only evaluated on first page load, it doesn't matter if it gets changed by other tabs later. Then use CSJS to navigate back.

You could consider an URL parameter, but I'd rather keep my URL clean

Stephan, yours approach sounds nice:) – dj_universe Feb 03 '16 at 08:17 — dj_universe, Feb 03 '16 at 08:17

Xpages ajax request impacts context history

2 Answers2