Skip to content

DOC-3147: Tab to create a new row in tables with a non-editable final row would freeze the editor. #3768

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

Open
wants to merge 1 commit into
base: feature/8.0.0/DOC-3147
Choose a base branch
from

Conversation

kemister85
Copy link
Contributor

Ticket: DOC-3147

Site: Staging branch

Changes:

Pre-checks:

  • Branch prefixed with feature/<version>/, hotfix/<version>/, staging/<version>/, or release/<version>/.

Review:

  • Documentation Team Lead has reviewed

@kemister85 kemister85 added this to the TinyMCE 8.0.0 milestone Jun 20, 2025
@kemister85 kemister85 requested a review from HAFRMO June 20, 2025 00:57
@kemister85 kemister85 requested review from abhinavgandham, soritaheng and a team as code owners June 20, 2025 00:57
@kemister85 kemister85 added the upcoming release Documentation for features currently under development/QA label Jun 20, 2025
@kemister85 kemister85 requested review from EkimChau, ShiridiGandham and MitchC1999 and removed request for a team June 20, 2025 00:57

Previously, when attempting to create a new row by pressing Tab in a table with a non-editable final row, the editor would freeze causing a infinite loop of insert attempts. This was due to the logic not correctly detecting whether the last row was editable, leading to repeated, unsuccessful insert attempts.

{productname} {release-version} fixes this issue by correctly detecting whether the last row is editable, allowing the user to create a new row without freezing the editor.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not quite correct, sorry for forgetting the docs.

Previously it didn't detect that the last row was readonly when tabbed into from above and instead created a copy of it. When attempting to place the cursor into it it found that it couldn't ( readonly after all ) and so created another copy and tried to go into that. This would then repeat until error.

The change is that it now detects that the last row is readonly and aborts creating another row before one has been added.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upcoming release Documentation for features currently under development/QA
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants