TypeCellOS / TypeCellOS/BlockNote

Keyboard navigation around images / tables / code blocks

Open
#2,514 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Bug bug:P2
Dominant language
TypeScript
Stars
10.2k
Forks
772
Avg merge
3d 11h
Merged PRs (30d)
17

Description

(parent issue)

What’s broken?

When having a single image in the editor, or adjacent block elements, it's not possible to move the image down with using just the keyboard. The gapcursor appears, but hitting enter does nothing.

Might need further exploration to see if there are related bugs.

related:
https://github.com/TypeCellOS/BlockNote/issues/2016

What did you expect to happen?

be able to use my keyboard just as well for blocks without inline content, as blocks with inline content

Steps to reproduce

No response

BlockNote version

No response

Environment

No response

Additional context

No response

Contribution
  • I'd be interested in contributing a fix for this issue
Sponsor
  • I'm a sponsor and would appreciate if you could look into this sooner than later 💖

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No files, tests, or entry points are named. Start by reproducing keyboard navigation in the BlockNote editor around single images, tables, and code blocks, then trace the related issue 2016; done means Enter and keyboard movement work for these blocks as they do for blocks with inline content.

Written by the indexing model from the issue text.

Assessment

Tech stack
react, typescript
Domain
frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
28/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.