I'm using the Facebook 'like' api for my site, but there is a bug on IE (tested on IE8, and reported on IE9).
Whenever I hit the back button, it's inserting the following two urls into the "Recent Pages":
https://s-static.ak.facebook.com/connec
http://static.ak.facebook.com/connect/x
and each time the back button is triggered, one more of this pair will be "inserted". For example:
1st: opening page A
2nd: going to page B
3rd: going to page C
4th: hitting back button OR Backspace button
5th: now i'm on page B, but now there will be two more url "inserted" to the back button, plus the forward button which is suppose to be able to bring me back to page C now is blank/cleared so won't able to use the forward button to go "back" to page C
Thanks for your help in advance,
Chi
Related
There are 3 screens in my app. When I use popAndPushNamed() in the 2nd page, it pops the 2nd page and shows the 3rd page, but when It pops it shows the 1st page behind it in milliseconds. how to avoid that?
is Animation the way?
or are there any other methods just like push and show 3rd page, and pop 2nd page when the 3rd page visible to the user?
popAndPushNamed() as the documentation suggests, pushes the new route but pops the old route simultaneously, and hence, there is a small moment where you can see the first page even if your new routes are fully opaque. Replace the method with Navigator.of(context).pushReplacementNamed() and it should work as expected.
I have a Browsing carousel in my Action that opens a new page. From that page, I want to give the user an option to either continue on the website or to close the website and go back to the Action.
If they select the option to go back - how can I send them back to the Action?
You can't "go back" to the Action in the same way as if you clicked on a back button in the browser.
However, you can create a link on the page that you're showing the user that will re-start the Action or re-start it with a particular "deep linked" Intent. If you maintain the state of the user when they leave your Action, you can restore that state when they return, but that is up to you to manage.
To create a link to start the Action go to your Action console, select the "Actions" navigation on the left, and then the right arrow for the Intent that you want to be able to link to.
Towards the bottom of the screen that comes up, you may need to click on the "Links" header to expand that section, and then turn the switch on for "Would you like to enable a URL for this Action?"
The section will expand to prompt you for a Link Title (which is required, but not really used for anything) and will show you an HTML code snippet with the link. You are allowed to change this link however you want, but you must use a link - you can't do something clever like try to redirect to that page.
I have a page hosted on, say, www.domainX.com. In my page there is an iframe, src attribute of which is set to www.domainY.com (so it's on another domain). There are some links on the page served from www.domainY.com (so they show up in the iframe). When I click one of these links there happens the navigation inside the iframe. Now, when I move the cursor on iframe, right-click and select 'Back' on the appearing menu, it makes a back in the inner iframe. If I do the same thing again, it does a back on the main window, as if I pressed the back button of the browser (or I right-clicked out of the iframe and selected 'Back').
My problem is: I am OK with back navigations in the iframe, but I do not want them to bubble up to the main window. I can alter the source code of the page on www.domainX.com, but I don't have access to the source code of the page on www.domainY.com . I tried attaching an 'onback' handler on the iframe element, which stops the event propagation; but it did not work. Any pointers will be appreciated.
Thanks
I'm having a problem with a facebook like button.
The problem is as follows:
When the user clicks the like button, a post-on-the-wall dialog appears (called with edge.create) but in just half a second, the dialog disappears.
Another thing is when you usually click a fb like button, your like is instantly processed, no problems here, but in my page, when you click the like button, the dialog windows appears, after a moment disapperas, and the text on the like button changes to "Confirm",
and only after pressing "Confirm", the like is processed.
(I am using the javascript api)
The problem should be obvious, but again - why does the dialog window disappear, and why does the like have to be "confirmed" ?
I've been banging my head with this problem for a few days and I really can't take it anymore, so any help would be GREATLY appreciated.
Thank you.
The confirm button usually shows up when a new like button is getting many clicks in a short time period to help battle "like-jacking". This is not a coding error, rather a facebook controlled function.
I have an activity with a mayStop() method. I am having two issues with it that pertain to a hyperlink on the page.
The first issue is that if I hit refresh or the window's X I get a dialog box that wraps my mayStop() text with "Are you sure you want to navigate away from this page?" and "Press OK to continue, or Cancel to stay on the current page." That is fine.
When I hit the hyperlink, I only see my mayStop() text without the wrapping text. Why is that?
The second issue is that if I hit Cancel in response to the hyperlink click, hitting the link again results in not getting the mayStop() challenge at all. It is as if I am not hitting the hyperlink.
Has anyone run into these issues?
Any thoughts?
Thanks,
Doug
The difference in "behavior" is that the first dialog box is the one from the browser when you try to prevent the user from navigating away, while the other is PlaceController calling Window.confirm(). Each browser uses a different dialog box for the first case, so there's no way to mimic it for everyone, and it's probably not a good thing either (navigating away from the app vs. navigating within the app).
As for your second issue, the events are generated by the browser "history" changing; if you prevent navigating away (from the Place), the URL stays the same (there's noway to know what to do to "rollback" the change: History.back(), History.next(), History.newItem() but then you destroy the existing "next" history ?), so when you click again on the link, you don't make the URL change, and no event is fired.
It's expected that you use PlaceController.goTo to navigate when you use places, not Hyperlink or History.