I'm implementing PayPal's In-Context flow for Express Checkout as specified in the documentation. Everything works as expected in Firefox, Chrome, and Opera. IE, however, gives me some issues.
When I click the "Checkout with PayPal" image, the page goes dark and the modal window opens above it to PayPal's login/signup page as it should. But just before the page loads in the modal window, the page behind it turns white again, allowing users to interact with it which it shouldn't. I'm still able to go through with logging in and things in the modal window, yet the page behind it is active.
The second issue deals with redirecting. In IE, the modal window NEVER disappears after clicking the "Continue" button, which redirects to a specified url on my server. The redirect happens alright; it just doesn't happen in the main window as it should but instead happens in the modal window. Simply put, everything that occurs after pressing the "Continue" button happens in the modal window with no more interaction with the main window.
Again, everything works in other browsers (I've yet to test things in Safari), but IE (v.11) isn't behaving correctly. Can someone point me in the right direction?
Thanks
I too had similar issue with IE/Firefox when I was using custom button images.
To overcome I just had to remove the button variable and let the javasript generate its own button.
window.paypalCheckoutReady = function() {
paypal.checkout.setup('S4X5XW328WAYY', {
container: 'myContainer',
environment: 'sandbox'
// button: 'incontext_id'//commented
});
Demo and PHP sample code here
Related
In my flutter app, I'm implementing a full page view using -
SystemChrome.setEnabledSystemUIMode(SystemUiMode.immersiveSticky);
Now, It works just fine until I reach a page in the app that uses PinCodeTextField. In that page, a user can input the received OTP.
Now, the issue is that as soon as the page is opened, "Auto-fill code from Messages" appears and it brings back the notification bar as well as the bottom menu bar.
I have not implemented this feature and looks like somehow It has come on its own. Though, it is a nice feature to have, I really don't want it to mess up my app's full page view. Not until I restart the app, it goes back to full page view but again whenever I reach to a page with PinCodeTextField, that popup appears and messes things up.
Now, how do I force my app to go back to full page view ? If that is not possible, how do I stop Auto-fill code to keep coming on my screen on such pages ?? Kindly help.
I am trying to automate a website interaction.
I can login programatically without issue.
Once I login I get to a page with a toolbar. When I hover over one of the options of the toolbar, the bottom of the ie screen displays a url that ends with .aspx.
When I navigate using $ie.navigate
$ie.Navigate("https://dcr.alleghenycounty.us/Civil/Filing/InitialCaseFiling.aspx")
, it redirects me to a page that tells me I need to log in. When I click manually works properly. There is no element for the drop down that I click on.
I am concerned that the navigate function causes the page to lose some kind of cookie.
I tried invoke-webrequest but it didn't do anything in the browser.
I tried appending the 2048 tag in the navigate command to open in new window.
Is there an alternate method of opening an .aspx?
I need to use powershell. I need to use internet explorer.
embedded a FB Send button using xfbml in an empty page.
Page hosted on RackSpace and has nothing else on it.
The button appears and works normally, but after ~10 seconds disappears - only on FF and IE, not on Chrome.
Facebook's xfbml code injects a span containing an iFrame that contains the button.
When looking at the style of the span it seems that in Chrome width=50px height=20px but in Firefox height=width=0. Changing that manually causes the button to reappear.
Would really appreciate your help.
Thanks,
Nir.
I am using Three20's WebController in my project and I am having issues with the 'back' arrow on the bottom controls (the <| button).
When I load a page and click a link in the WebController you'd expect the back button to enable and if touched bring you back to the original page.
But when I hit a link from the original page the back button is not always working, it stays disabled therefore you cannot go back to the original page.
It does sometimes work, but it seems random and its rare it does. I looked in the source for three20's WebController and all its doing is using a UIWebView's goBack function. But as I said it does work sometimes, but not most of the time.
I have searched the net but found no other reports of this issues, does anyone have any suggestions?
Thanks!
I was able to find my solution. I traced the code and [_webView canGoBack] was returning NO, it was because I was not loading a request, I was rather loading an HTML string which wasn't being saved for use in the back button.
I changed my code back to loading requests and it fixed the issue.
Solution was found here:
http://www.iphonedevsdk.com/forum/iphone-sdk-development/18870-uiwebview-cangoback-always-returns-no.html
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.