Hi,
I have problem that drives me creazy. I have a tracking script that runs on the websites of our customers.
The problem is the following:
- When a visitor visits a page a javascript triggers a dom created IFRAME that locates to a file on the server of out customer.
- This file (WebServiceClie nt.html) is posting automatically (DOM) to a Webservice running on our cloud, so we can save visitor data.
So far so good. The problem rises when a visitor runs a page with our script and wants to navigate back.
Because the underlying IFRAME is doing an invisible post the Browser thinks to go back to the post or the IFRAME source page when back is clicked.
My question is: how can I solve this? I just want the navigation button to work correctly.
The code works fine and we decided to use this architecture so we could evase the problem of the long load time. Since the server of our customer is posting to a external webservice that threats the connection and disposes it, the load time is 0.
Any help is welcome.
I have problem that drives me creazy. I have a tracking script that runs on the websites of our customers.
The problem is the following:
- When a visitor visits a page a javascript triggers a dom created IFRAME that locates to a file on the server of out customer.
- This file (WebServiceClie nt.html) is posting automatically (DOM) to a Webservice running on our cloud, so we can save visitor data.
So far so good. The problem rises when a visitor runs a page with our script and wants to navigate back.
Because the underlying IFRAME is doing an invisible post the Browser thinks to go back to the post or the IFRAME source page when back is clicked.
My question is: how can I solve this? I just want the navigation button to work correctly.
The code works fine and we decided to use this architecture so we could evase the problem of the long load time. Since the server of our customer is posting to a external webservice that threats the connection and disposes it, the load time is 0.
Any help is welcome.
Comment