Skip to content

feat(executor): add tab character to tab node conversion in text insert#2832

Open
andrii-harbour wants to merge 1 commit intomainfrom
andrii/sd-2567-api-tabs-export
Open

feat(executor): add tab character to tab node conversion in text insert#2832
andrii-harbour wants to merge 1 commit intomainfrom
andrii/sd-2567-api-tabs-export

Conversation

@andrii-harbour
Copy link
Copy Markdown
Contributor

No description provided.

@andrii-harbour andrii-harbour self-assigned this Apr 15, 2026
@linear
Copy link
Copy Markdown

linear bot commented Apr 15, 2026

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f4a3cd90a8

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

Comment on lines +973 to +974
const tabNodeType = editor.state.schema.nodes.tab;
if (tabNodeType && text.includes('\t')) {
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Validate tab-node insertion against parent content expression

This branch converts any \t to schema.nodes.tab whenever the tab type exists, but it never verifies that a tab node is valid at absPos. That regresses cases where text insertion happens inside containers that allow only text* content (for example total-page-number in extensions/page-number/page-number.js): previously a raw tab character could be inserted as text, but now tr.insert(absPos, fragment) can throw a schema replace error and abort the whole plan execution. Please check parent compatibility (canReplace/canInsert) and fall back to text-node insertion for tabs when tab is not allowed at the target position.

Useful? React with 👍 / 👎.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants