Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Dropdowns in MCP forms not working #3029

Closed
MANID048 opened this issue Jan 20, 2023 · 4 comments
Closed

Dropdowns in MCP forms not working #3029

MANID048 opened this issue Jan 20, 2023 · 4 comments
Assignees
Labels
Milestone

Comments

@MANID048
Copy link

Required Information

  • AEM Version, including Service Packs, Cumulative Fix Packs, etc: AEM as a Cloud Service latest release
    ACS AEM Commons Version: 5.4.0
    Reproducible on Latest? yes

Expected Behavior
Dropdown fields within the MCP form should expand upon being clicked.

Actual Behavior
Dropdown fields within the MCP form do not expand upon being clicked.

Steps to Reproduce
Go to Tools > ACS AEM Commons > Manage Controlled Processes.
Click "Start Process" in the top-right corner.
Select a process that has a dropdown in the form (e.g. "Asset Folder Creator").
Try to expand the dropdown.

@MANID048
Copy link
Author

#2277. Same issue still there

@davidjgonzalez
Copy link
Contributor

It appears the problem is because the forms with the (coral) select are XHR'd in and injected into the "ready" DOM. Something changed where whatever initializes the select dropdown isnt triggering after the DOM injection. I've reached out to product to see if they have a solution to work around this change.

davidjgonzalez added a commit to davidjgonzalez/acs-aem-commons that referenced this issue Jan 20, 2023
@davidjgonzalez
Copy link
Contributor

This should fix it:
#3030

@davidjgonzalez davidjgonzalez self-assigned this Jan 20, 2023
davidjgonzalez added a commit that referenced this issue Jan 20, 2023
* #3029 - Fixed dropdowns in MCP process forms
@davidjgonzalez davidjgonzalez added this to the 5.5.2 milestone Jan 20, 2023
@davidjgonzalez
Copy link
Contributor

Fixed in v5.5.2 (just released)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants