# Can't write in the custom inline text node after it is moved to a new line

**URL:** <https://discuss.prosemirror.net/t/cant-write-in-the-custom-inline-text-node-after-it-is-moved-to-a-new-line/8402>\
**Category:** Uncategorized\
**Created:** [May 11, 2025, 11:32am UTC](https://discuss.prosemirror.net/t/cant-write-in-the-custom-inline-text-node-after-it-is-moved-to-a-new-line/8402 "2025-05-11T11:32:50Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![marijn](https://discuss.prosemirror.net/user_avatar/discuss.prosemirror.net/marijn/32/15_2.png) [@marijn](https://discuss.prosemirror.net/u/marijn)\
**Post date:** [May 11, 2025, 12:18pm UTC](https://discuss.prosemirror.net/t/cant-write-in-the-custom-inline-text-node-after-it-is-moved-to-a-new-line/8402/2 "2025-05-11T12:18:55Z")

</div>

The answer here is pretty much the same as in [this thread](https://discuss.prosemirror.net/t/why-backspace-at-a-line-start-converts-custom-inline-node-to-text/8401): Non-atomic inline nodes will need a bunch of scripting to behave well. ProseMirror is relying on the browser’s native cursor motion and positioning, and Chrome won’t even let you put your cursor into the span element. Firefox kind of does, and lets you type into it, but once you move out of it you cannot move back. You’d have to override cursor motion keys to make this work. Or, which is often a better solution, use a mark instead of a node.

---

_[View the full topic](https://discuss.prosemirror.net/t/cant-write-in-the-custom-inline-text-node-after-it-is-moved-to-a-new-line/8402)._