Bug 1368499

Summary: Disable double click on UI when displaying Service -> Request items to display provision requests
Product: Red Hat CloudForms Management Engine Reporter: Aziza Karol <akarol>
Component: UI - OPSAssignee: Milan Zázrivec <mzazrivec>
Status: CLOSED WONTFIX QA Contact: Dave Johnson <dajohnso>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.6.0CC: hkataria, jhardy, mkanoor, mpovolny, obarenbo, tfitzger
Target Milestone: GA   
Target Release: 5.7.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: ui:provisioning
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-29 12:46:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Aziza Karol 2016-08-19 14:57:40 UTC
Description of problem:
Opening this issue with reference to bz 
https://bugzilla.redhat.com/show_bug.cgi?id=1364350


Version-Release number of selected component (if applicable):
5.6.1

How reproducible:
100%

Steps to Reproduce:
UI allows a double click,disable the second click and should not be allowed to repeat the same thing again.
There seems to be an issue with Automate not being to handle concurrent requests
because of DRb. 

Actual results:


Expected results:


Additional info:

Comment 2 mkanoor 2016-08-19 15:02:20 UTC
We have fixed this issue in Automate by using separate Drb server instances. But not sure why the UI would be unnecessarily sending back to back requests. This was in the Service -> Requests screen, where we display the list of Requests.

Comment 4 Milan Zázrivec 2016-08-29 12:46:47 UTC
UI isn't sending double clicks unnecessarily here. If you simply click twice
(double click) on the service request row, your browser will also do
the GET request twice. Nothing less, nothing more.

I could prevent the double click here to be sent, but I'm not going to do that, since:

1. I'd have to do this by setting a timeout of an arbitrary length on a single click event
2. We'd have to do this consistently in the whole UI in some sort or fashion
3. If the "double click" here causes problems on the backend, then it's the backend part
here that needs to be fixed, since in general we cannot prevent the two (or more) subsequent
requests to be done by other means beside our UI.

I'm closing this with wontfix.