Hello Ambari Community, As we approach the release of Ambari 3.0.0, I want to first express our gratitude to all contributors for their valuable work. During our recent validation process, our team member zrain has identified and investigated a user experience issue that we'd like to bring to the community's attention.
## Issue Description We've discovered a bug affecting the checkbox behavior in the host configuration step during cluster initialization or service addition. This issue has been tracked as [AMBARI-26192](https://issues.apache.org/jira/browse/AMBARI-26192) and impacts user experience but does not prevent core functionality. ### Technical Details Through zrain's investigation, the issue was found to manifest in the following files: - Template: `ambari-web/app/templates/wizard/step6.hbs` - View: `ambari-web/app/views/wizard/step6_view.js` Current implementation: ```html <div class="checkbox" {{bindAttr data-qa="checkbox.dataQaAttr"}}> <input {{bindAttr id="checkbox.uId" checked="checkbox.checked" disabled="checkbox.isDisabled"}} {{action "checkboxClick" checkbox target="view"}} type="checkbox"/> <label class="host-component-checkbox" {{bindAttr for="checkbox.uId"}}>{{checkbox.title}}</label> </div> ``` ```js checkboxClick: function (e) { var checkbox = e.context; Em.set(checkbox, 'checked', !checkbox.checked); this.get('controller').checkCallback(checkbox.component); this.get('controller').callValidation(); } ``` ### Bug Behavior Based on zrain's detailed exploration, when the checkbox's CSS display property is set to non-none: 1. Unchecking a checked checkbox works correctly 2. Attempting to check an unchecked checkbox fails visually 3. The checked property is set correctly in the background 4. The :checked CSS selector fails to take effect Our investigation suggests this is likely due to incompatibility between the upgraded jQuery version and EmberJS event management mechanism. ## Impact and Release Plan While this issue affects user experience, it does not prevent core functionality as users can still complete their tasks through alternative means. However, we want to be transparent about our release strategy: 1. We are actively seeking community input for a fix 2. We will allow one week for community feedback and potential fixes 3. If no solution is found within this timeframe, we plan to proceed with the release 4. The issue will continue to be tracked under AMBARI-26192 and addressed in a subsequent release if not resolved before release ## Request for Input We welcome any suggestions or contributions from the community, especially from those with experience in: - EmberJS event handling - jQuery-EmberJS integration - Frontend event management systems Please share your thoughts, experiences, or potential solutions in the JIRA ticket [AMBARI-26192](https://issues.apache.org/jira/browse/AMBARI-26192). We've documented some potential approaches and are open to additional suggestions. ## Next Steps 1. Community feedback period: 1 week 2. If no blocking issues are found, proceed with release 3. Continue tracking and working on fix in AMBARI-26192 Thank you for your continued support and collaboration. Best regards, JiaLiangC --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
