DescriptionFelix Dewaleyne
2018-03-23 17:14:56 UTC
Description of problem:
in certain situations the refresh methods are called on every single refresh
Version-Release number of selected component (if applicable):
5.9.0
How reproducible:
all the time
Steps to Reproduce:
1. create a dialog with two text fields with no refresh relation between them, showing their refresh buttons.
2. associate each to a different method that just logs 'Refreshing X'
3. associating the dialog to a catalog item
4. tail -f log/automation.log | grep "Refreshing"
5. load the dialog
6. click "refresh" for field 2
Actual results:
When you click on refresh you can see the refresh method for field 1 has been called before that of field 2 and followed by another run of the method of field2
Expected results:
when clicking refresh for text field 2 only text field 2 is refreshed
Additional info:
this can't be reproduced if using 2 droplists instead of two textfields.
(In reply to Chris Pelland from comment #7)
> Is this a Duplicate of this BZ?
> https://bugzilla.redhat.com/show_bug.cgi?id=1571000
not sure. this issue was limited to a type of field. it's possible that more elements are affected than the textfield one.
this was opened against 5.9.0, but the other is against 5.9.1, could be that the problem worsened with the errata.
Comment 10Niyaz Akhtar Ansari
2018-09-04 11:56:17 UTC
Verified in Version 5.10.0.14.20180831154906_2f9a1dd