Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 1363882

Summary: Text dialog updates fire too many events causing delays
Product: Red Hat CloudForms Management Engine Reporter: Colin Arnott <carnott>
Component: UI - OPSAssignee: Martin Hradil <mhradil>
Status: CLOSED ERRATA QA Contact: Shveta <sshveta>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.6.0CC: benglish, hkataria, jhardy, mpovolny, obarenbo, simaishi
Target Milestone: GAKeywords: ZStream
Target Release: 5.7.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: dialog
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1372767 (view as bug list) Environment:
Last Closed: 2017-01-04 12:58:59 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1372767    

Description Colin Arnott 2016-08-03 19:43:21 UTC
Description of problem:
As a user when I enter text into fields in a service dialogue many POST update events are fired causing extensive delays in the value actually being updated for the dialogue.

When I select all of the text and press delete there are also many events sent.

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

Steps to Reproduce:
Any time the user clicks the button for the dynamic dialog prior to all of the update events being sent and processed by MIQ. For a proficient typist this happens most of the time.

Additional info:
I am including a video showing the extensive delay seen and the many POST update events sent

Comment 7 Shveta 2016-09-21 04:30:32 UTC
Fixed.Verified in

Comment 10 errata-xmlrpc 2017-01-04 12:58:59 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.