Display glitch when pressing Enter or Backspace in Scrivener (Mac, latest version)

Hi all,

I’m running into a strange display glitch in Scrivener (latest version, 3.4) on my MacBook (mac os 15.2). Typing itself works fine, but when I insert new lines with Enter or jump back with Backspace, the editor glitches:

  • A line of text suddenly disappears from view
  • The bottom line of text is displayed twice
  • Or only a few millimeters of the last line of text are visible, making it look like unreadable gibberish.

This only affects the way the text is displayed, the content itself remains intact and reappears once I scroll, type, or otherwise refresh the editor. I’ve added a video to show the glitch, not sure if this works though.

Has anyone else experienced the same behavior and knows a solution?

1 Like

Is there a reason you don’t run the latest Version of macOS 15? The latest version is 15.6, and since Scrivener uses Apples TextEngine, maybe the glitch you described has been fixed since 15.2.

1 Like

I work as an illustrator and I avoid updating macOS while working on a book project (there’s always the risk that my ancient drawing tablet or scanner might stop working after an update.) As for whether this is an Apple TextEngine issue, if the problem doesn’t appear in other writing apps, isn’t it possible that it may be more specific to Scrivener rather than the underlying text system?

Check TextEdit specifically, as applications like Word use their own toolkits.

FWIW, display glitches are fairly common in early versions of any Mac OS release.

From our perspective, we wouldn’t consider it an actionable bug unless we were able to reproduce it in the current Mac OS version. (And even then, if it derives from the text system there might not be much we can do.)

1 Like

Okay, I understand. Thank you Suavito and Kewms, I will update to the current Mac OS and report back!

I’ve updated to the latest OS. The bug is not in TextEdit, only in Scrivener.

Please open a support ticket, here:

That’s easier to tie into our bug tracking system.

1 Like

That is a wise way to handle things. Well: was. I hope, I haven’t lured you into a situation that is of dire consequence to you.

I have been seeing what is plausibly the same (or related) bug for a good long time now: (Pardon the typo.)

Note position of insertion point. Below is result of hitting return.

The second paragraph is not gone, but certainly something presentational has not updated correctly.

1 Like