chromedome1981
Newbie
- Nov 19, 2020
- 2
- 3
I have a job for a client-side guru, involving Google Chrome and redirects.
Chrome has adapted the way it deals with redirects and the back button where pages that use redirects without human interaction are skipped when the back button is pressed. I'm looking for a solution that doesn't require human interaction to overcome that behaviour.
So
/a.html, click on a link to /b.html which 3 seconds later redirects to /c.html. After clicking back, I want to be on /b.html but Chrome will take you back to /a.html.
This centres around the event.isTrusted property and anyone who does this kind of thing will know the general problem.
To anyone who can provide me with a working solution, 500 GBP is on offer.
Chrome has adapted the way it deals with redirects and the back button where pages that use redirects without human interaction are skipped when the back button is pressed. I'm looking for a solution that doesn't require human interaction to overcome that behaviour.
So
/a.html, click on a link to /b.html which 3 seconds later redirects to /c.html. After clicking back, I want to be on /b.html but Chrome will take you back to /a.html.
This centres around the event.isTrusted property and anyone who does this kind of thing will know the general problem.
To anyone who can provide me with a working solution, 500 GBP is on offer.
