ueberdosis/tiptap

"No value supplied for attribute class" error when passing undefined class to HTMLAttributes in Link

Open

#7214 opened on Nov 12, 2025

View on GitHub
 (1 comment) (0 reactions) (0 assignees)TypeScript (23,454 stars) (1,979 forks)batch import
area: coregood first issuejavascriptstatus: triage

Description

Affected Packages

extension-link

Version(s)

3.10.5

Bug Description

When you pass an undefined class to HTMLAttributes when configuring a link, it causes the following error: No value supplied for attribute class

eg.

Link.configure({
  HTMLAttributes: {
    class: undefined
  },
}),

Browser Used

Chrome

Code Example URL

https://codesandbox.io/p/sandbox/trusting-glitter-nyl9g3

Expected Behavior

Should throw an error but not crash when passing an undefined class

Additional Context (Optional)

No response

Dependency Updates

  • Yes, I've updated all my dependencies.

Contributor guide

Tech stack
typescript
Domain
frontend
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
basic TypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
90
Research direction
Look at the extension link package in the tiptap monorepo, specifically the Link extension configuration where HTMLAttributes are processed. The issue is that undefined values for 'class' are not filtered out before setting attributes. The fix likely involves adding a check to skip undefined values when merging HTMLAttributes into the DOM element.