-
Notifications
You must be signed in to change notification settings - Fork 464
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
[Containers] : Save button is disables under specific circumstances #24164
Comments
2 tasks
zulqarnainvd
added a commit
that referenced
this issue
Feb 22, 2023
zulqarnainvd
added a commit
that referenced
this issue
Feb 24, 2023
zulqarnainvd
added a commit
that referenced
this issue
Feb 24, 2023
3 tasks
fmontes
pushed a commit
that referenced
this issue
Feb 28, 2023
Passed Internal QADocker Image: [ save-button-must-be-enabled-after-any-change.mov |
Approved QA - Tested on 23.03_5ce847f3_SNAPSHOT // Docker // macOS 13.0 // FF v110.0 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Problem Statement
The
SAVE
button is not being enabled when trying to add a new Content Type to a new Container.Steps to Reproduce
Max Contents
field, so that theContent Type Code
field shows up.Contact
content type.SAVE
button is not enabled. Even if you try to change the Container's name or description, it remains disabled.Acceptance Criteria
The
SAVE
button must be enabled after any change is made.dotCMS Version
Latest master.
Proposed Objective
Technical User Experience
Proposed Priority
Priority 2 - Important
External Links... Slack Conversations, Support Tickets, Figma Designs, etc.
Found during IQA of #23443
Assumptions & Initiation Needs
If you type in any characters for the default
Activity
content type, then theSAVE
button is enabled. This is the only way to make it work. So there seems to be a problem with JS events at some point?Sub-Tasks & Estimates
No response
The text was updated successfully, but these errors were encountered: