I would like to discuss one browser's behavior:
User is on PLP (product listing page of any e-commerce site) and is using mobile device.
After scrolling down (like after scrolling 30~45 tiles), user opens a PDP (Product Display Page) by clicking on a product.
Then he clicks the back button and move back to the PLP. He'll be moved to the location where he clicked the product.
This is a browser's behavior, which is soo cool!!!
But - my concern is that 'sometimes', user is redirected to some other part (above the point where user clicked the tile) of PLP screen (not from where he opened the PDP).
It could be an issue in the browser history being updated/not updated. Can anyone help in concluding the issue here?
Related
Scenario:
I enter a web page
Page shows desired content for a few seconds
It reloads and opens another web page (within the same tab, no new tab is fired - usually an ad)
I press the back button and the desired page opens again
How can i block this behaviour having only the desired page displayed, without reloading.
What actually causes this? I have some extensions for blocking redirects, but they work only on new tab redirects.
I am also a software engineer so a technical explanation would help me, if possible.
A client wishes to have a link that opens a new window and shows the website of an investment company.
Pretty straight forward so far.
So I create this link
Click Me
The client then tells me that the page is acting all weird. So I test it and he's right, it's acting very strange.
Here's what my tests shows.
Firefox mac: Page opens, then closes itself and returns to the window with the client's website where it then changes the URL to the one that is suppose to open.
Safari mac and Chrome mac: Page opens, then closes itself and returns to the window with the client's website
Client's IE: opening and closing multiple windows (his words, didn't test it myself);
Instead of redirecting to the page itself, I changed the link to go to the homepage. User will now have to click on "Login" to access the page we wanted originally. Guess what? It does the same thing.
Here's a simplified fiddle. You'll see it's pretty straight forward.
Now I know that the problem isn't from my side but on the investment site. They seem to dynamically add some parameters to the URL for security reasons I suppose.
My question is: how can I avoid all this non sense and simply open the page without it closing? Can someone explain to my why it's doing so?
I tried the login link myself (in Chrome) and it does the same thing.. closes itself.. You should contact their web-designers and report the problem. I succeeded to click on Stop loading button and look through page. Everything is "ok" except that thing it closes. Contact them and wait for response/fix.
I am creating a webpage and am having some issues with how the back button works on the page. I am guessing that I need to set some headers, but don't know which ones or how. This is what I'm seeing:
(1) Go to the main page, which shows forum threads.
(2) Click a link to go to a page showing a thread. On this page, scroll down and add a comment.
(3) Comment is saved via form (edit: I have tried both POST and GET form). The same thread page is now reloaded via a redirect. The comment shows.
In Chrome: pressing the back button at this point still shows the comment as having been added. It looks as though the back button didn't work. However, the page is scrolled down as it was for (2). Clicking the back button again shows the main page. So, the back button does take me back, but if the same page is there twice, it shows the new data both times.
In IE9: pressing the back button displays "Webpage has expired". Clicking it again takes me to the main page.
How do I alter this behavior so the back button truly shows me the previous page?
(The reason I'm doing this is that I keep track of how many pages I am from the main page so I can generate a "back to main page" link. (2) above has history.go(-1) and (3) above has history.go(-2). This won't work if the user presses the browser back button from (3) since it will now be 1 away from the main page, but show the link from (3).
In step (3) you probably have a POST that returns the new HTML of the thread page. Instead the POST should redirect to a GET of the thread page.
See http://en.wikipedia.org/wiki/Post/Redirect/Get
I have a problem and I think the best thing is to describe it practically:
User is on the main window (this is properly called "main-window" via JavaScript: self.name = "main-window";)
User clicks on a link that opens in a new window
From the new window, user clicks on a link like: <a href="..." target="main-window">
The expected behaviour is the browser to focus on the main window ("main-window") and open the requested page (IE and Chrome do this correctly). Firefox opens the link in the main window, but doesn't focus on it. The result is that the user wonders why the link doesn't work since he doesn't realise that it opens on the window behind the current one.
Is this a known issue? Is there any solution?
Thank you.
I've been looking for an answer everywhere and cannot find the answer to this, I have absolutely no idea what I'm doing wrong.
I created a custom tab for my page, and I set the default landing tab for the page to this custom tab, however whenever you visit the page it just goes straight to the wall.
I don't want people visiting my page to land on my wall, I want them to land on the custom tab, that's why I created it.
How do I get the default landing tab option to work for my pages? They're all doing this.
If you already "like" the page (or are an admin), it will always take you to the wall. If you are not a fan or an admin, it will show you the tab specified. That is how these tabs work, there is not an always to always show the tab for fans.