There is a need to retest and compare the functionality between the old and new WYSIWYG editors on WYSIWYG fields in dotCMS. This includes verifying feature parity, user experience, and overall performance between the two versions. Notably, the plain text mode will be removed in the new editor, so it is important to assess how this change impacts the content editing workflow.
Ensuring that the new editor offers all necessary functionalities without the plain text mode is critical for maintaining a seamless content creation experience for users.
Proposed Objective
Quality Assurance
Proposed Priority
Priority 2 - Important
Acceptance Criteria
Ensure that all core WYSIWYG functionalities (text formatting, media insertion, table management, a-checker etc.) are present and work as expected in the new editor.
Confirm that removing the plain text mode in the new editor does not negatively impact the user experience.
Identify and document any feature gaps or regressions between the old and new editors.
Provide to R&D team a list of test cases for this feature in order to retest before enable this feature.
Task
There is a need to retest and compare the functionality between the old and new WYSIWYG editors on WYSIWYG fields in dotCMS. This includes verifying feature parity, user experience, and overall performance between the two versions. Notably, the plain text mode will be removed in the new editor, so it is important to assess how this change impacts the content editing workflow.
Ensuring that the new editor offers all necessary functionalities without the plain text mode is critical for maintaining a seamless content creation experience for users.
Proposed Objective
Quality Assurance
Proposed Priority
Priority 2 - Important
Acceptance Criteria