| Summary: | Tag control dropdown is broken | ||
|---|---|---|---|
| Product: | Red Hat CloudForms Management Engine | Reporter: | John Prause <jprause> |
| Component: | UI - OPS | Assignee: | Martin Hradil <mhradil> |
| Status: | CLOSED ERRATA | QA Contact: | Milan Falešník <mfalesni> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 5.5.0 | CC: | carnott, cpelland, dclarizi, hkataria, jhardy, jprause, kmorey, mfalesni, mhradil, mpovolny, nstephan, obarenbo, ssainkar |
| Target Milestone: | GA | Keywords: | ZStream |
| Target Release: | 5.5.4 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | ui:automate | ||
| Fixed In Version: | 5.5.4.1 | Doc Type: | Bug Fix |
| Doc Text: |
Previously, service dialog tag control dropdown rendered but broke when clicked.
This patch fixes miq_observe functionality on selectpickers. This fixes initializeDialogSelectPicker to not assume trigger_auto_refresh by default and calls that instead of miqInitSelectPicker + miqSelectPickerEvent (both are called from initializeDialogSelectPicker) also selectedValue is made optional (because it is already handled by select_tag). Also, the data-miq_observe attribute has been removed from drop_downs, since that functionality is handled by miqSelectPickerEvent for selectpickers.
|
Story Points: | --- |
| Clone Of: | 1302331 | Environment: | |
| Last Closed: | 2016-05-31 13:41:35 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: | 1302331 | ||
| Bug Blocks: | |||
|
Comment 5
Harpreet Kataria
2016-05-10 20:50:01 UTC
Verified in 5.5.4.2. The tag control field works and passes the value. 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. https://access.redhat.com/errata/RHBA-2016:1101 |