[Bug]: Caps lock + enter create two list items

[Gaurussel]

Affected Packages

extension-bulletlist, extension-orderedlist, extension-tasklist

Version(s)

latest

Bug Description

With enabled "Use caps..." in macOS settings on pressing capslock with enter created two list items.

Browser Used

Chrome

Code Example URL

No response

Expected Behavior

Created only one list item

Additional Context (Optional)

Screen.Recording.2025-01-17.at.20.34.50.mov

Dependency Updates

• Yes, I've updated all my dependencies.

[Nantris]

It would be useful to document what events are firing in the keydown and beforeinput listeners. You can make a ProseMirror plugin using handleDOMEvents to log them out.

[guanriyue]

This is neither a Tiptap issue nor a ProseMirror issue. It seems there is some special handling of keyboard events in the browser.

I used a plain <textarea> to demonstrate. After pressing Caps Lock, if you immediately press a number or letter key, such as the number 9, it will trigger KeyboardEvent[key=Unidentified] once, followed by another KeyboardEvent[key=9]. However, if you immediately press the Enter key, it will trigger two consecutive KeyboardEvent[key=Enter] events.

2025-01-20.15.49.29.mov

For the Unidentified case, refer to MDN documentation. But why is the Enter key recognized correctly? I don't have experience with this kind of issue. In fact, I also tried Backspace, and it too was triggered twice.

You might consider reaching out to ProseMirror's author, Marijn, for advice. The addKeyboardShortcuts feature essentially uses prosemirror-keymap under the hood. In your example, the Enter key event triggered ListItem.addKeyboardShortcuts.Enter. Naturally, since two KeyboardEvent[key=Enter] events were dispatched due to input behavior, the shortcut was triggered twice, resulting in two listItem elements being added.

[guanriyue]

It seems that this behavior triggers the beforeinput event only once (and the keypress event also triggers only once), which might be helpful in resolving this issue.

[nperez0111]

I think this would probably have to be handled by prosemirror, not here