I have issues like Chase PaymentGateway iframe causing Multiple or duplicate payment when hitting submit button twice. Due to increased activity, we are seeing the iframe is slow to respond. and when users click the Submit button more than once or hit the Back button to resubmit your payment. which is resulting in duplicate payments.
any suggestion in avoiding it ?
Related
I want to disable the button once clicked in Webchat/Directline channel.
Once a user has clicked on a button, that button should get disabled to prevent duplicate usage of the button.
In case it was missed in the linked GitHub issue, using the method described in the BotFramework-WebChat sample 05.custom.components/l.disable-adaptive-cards will achieve this for you.
In short, you are creating an attachment middleware that filters incoming attachments on their type. Internally, when Web Chat detects you have clicked the adaptive card button the to-be rendered HTML for the adaptive card is then given the disabled tag.
I've tested this many times and it works. It should for you, as well.
Using visual studio and have a web app (MVC/API) that i want to inspect/profile using Glimpse.
I have glimpse enabled and have navigated to a specific page on a web app. so far I can see a lot of data has been collected. I now want to capture what happens when I press a button.
How do i clear previous data so glimpse only shows data related to the interaction interest?
If the button click triggers a new page navigation, Glimpse will automatically clear the old data that you are seeing.
If it triggers an ajax request, click on the Ajax tab and select the request that was just made. All of the data in Glimpse will update to show you the info for just that ajax request.
Similarly, you can do the same thing with the history tab to see past data for past requests.
Assuming the following scenario:
User is on product list page
Clicks a product and is redirected to the product detail page
Clicks on purchase button
POST /products/1/purchase/ is executed and redirects back to product detail page
User clicks back button
POST /products/1/purchase/ is executed again (FAIL! it should have been redirected to product list page)
How would you solve the back button problem?
Is there any response code that forces the browser to skip the location from history stack?
Assuming I can implement my own back button, how would you implement it?
Manually tracking the history, client-side
Manually tracking the history, server-side
Setting checkpoints and redirecting back to the checkpoint in case of existence
See:
Back button re-submit form data ($_POST)
I'm facing a strange problem here, i have used a sample code of graph api's (reallylongaddress-iPhone-Facebook-Graph-API-59e6399, Created by , https://github.com/reallylongaddress/iPhone-Facebook-Graph-API) which was available on github. And i faced these problems:-
1) I'm having a share button of my own , when i click on it to login to fb a white view (or popup ) apears for almost 5 seconds and it appears evry time when i click on share button to share something on my facebook wall, even if i'm logged in . I reduced this problem to only one time.
2) The second and main problem now i'm facing is that on login it doesn't have any close button on it , and user must have to login ,other wise the application will not continue. Can i place a close button on this fb login web view?
NOTE:I have also used the fbconnect earlier but i dont wanna use publish dialog box ,, which shows user a dialog box and then user can press on "pulish" or "skip" button. instead i want that what ever the user wants to share on wall can be shared on just one tap on a button. That is why i have used this sample code, but it also has these two problems i have specified above.
Please help me with these 2 problems above or suggest me any other alternative option which does not have the "publish.stream" dialog box.
Thanks
In this condition Facebook controller are called by UINavigationController.
Finally i solved the problem and placed a close button on the login view. and on tab of this button i closed the login web view
I want to know how you guys deal with back button issues in your web applications.
I can not forbid users to click back button on their browser, but when they hit it, the page code doesn't run. So writing in page_load() makes no sense.
I have searched online and found this link: Disabling Back button on the browser. It does not work for me. Any idea?
There is no way to disable the back button. You can try to open your page/form in a new window so there would be nothing to navigate back to
Normally, If I have a critical or lengthy form, I tend to maintain a dirty-flag and if the user starts entering something, the dirty-flag gets set and on save or submit it gets reset. You can use unload/beforeunload javascript event to see if the dirty-flag is set and ask for confirmation.