Skip to content

Navigation Menu

Explore
By company size
By use case
By industry
View all solutions
Topics
- AI
- DevOps
- Security
- Software Development
- View all
Explore
- GitHub Sponsors
  Fund open source developers
- The ReadME Project
  GitHub community articles
Repositories
- Enterprise platform
  AI-powered developer platform
Available add-ons
Pricing

Search code, repositories, users, issues, pull requests...

Search

Clear

Search syntax tips

Provide feedback

We read every piece of feedback, and take your input very seriously.

Include my email address so I can be contacted

Saved searches

Use saved searches to filter your results more quickly

Name

Query

To see all available qualifiers, see our documentation.

You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session. You switched accounts on another tab or window. Reload to refresh your session.

Dismiss alert

ueberdosis / tiptap Public

Notifications You must be signed in to change notification settings
Fork 2.3k
Star 28.2k

Code
Issues 517
Pull requests 36
Discussions
Actions
Projects
Security
Insights

Additional navigation options

Code
Issues
Pull requests
Discussions
Actions
Projects
Security
Insights

Fix getMarkRange not finding marks when at the start of a mark#5717

Merged

bdbch merged 5 commits intodevelopueberdosis/tiptap:developfrom fix/get-mark-rangeueberdosis/tiptap:fix/get-mark-rangeCopy head branch name to clipboard

Oct 11, 2024

+154-3

Conversation Commits5 (5)Checks Files changed

Commits

Commits on Oct 10, 2024

fix getMarkRange to always find a mark, even if cursor is at start of mark
bdbch
committed
added changesets
bdbch
committed
added integration tests for getMarkRange
bdbch
committed
remove console.logs
bdbch
committed
added forward and backward boundary checks for tests
bdbch
committed

Footer

© 2025 GitHub, Inc.

Footer navigation

Terms
Privacy
Security
Status
Docs
Contact

You can’t perform that action at this time.