Hey! I updated to the interim 3.45 build with support for Tahoe and it’s been working flawlessly for writing novel writing, some essays and a stage play but using the built-in screenplay template (or even switching to scripwriting mode on any document, new or old from previous versions) has a typing delay issue when you’re writing stuff that you can press TAB to complete (ie. scene headings, transitions) and it takes a couple seconds for whatever you typed to register on screen. I assume this has to do with Apple not fixing certain bugs, because navigating the OS in Tahoe itself has some quirks and minor bugs/stuttering/choppiness that make me wish I had stayed on Sequoia. 
I’m not able to reproduce this, unfortunately - hitting tab in scriptwriting mode works fine for me. Do you by any chance have any software installed at all that might check for keystrokes (such as TextExpander)?
I might actually! I have an app called Klack (from the App Store) which basically checks for mouse clicks and keyboard presses to recreate a mechanical sound). I turned it off and uninstalled it, but the issue persists which is weird. I should also specify I’m using an M1 Max MacBook Pro, but no other app seems to encounter this issue (I tried Final Draft 13 and the problem doesn’t appear there).
The issue specifically isn’t pressing tab, but what I run into is when manually typing a scene heading, transition, name, or anything else that has the pop-up menu to be completed. For example, I choose scene heading as my element. I’m writing EXT. but there’s small delay in between pressing characters when I manually type out EXT. instead of pressing tab to auto-complete it.
Sorry I’m not that great at explaining. I can send a video if that helps?
A video would be great, thanks. I’m off for the weekend now, but I’ll take a look at it next week.
Hang about! What’s this weekends off? 
3 Likes
@SebastianLarrs thanks for sending the video, which clearly shows a strange delay going on. Unfortunately I’m still unable to reproduce the problem. I tested it on my MacBook Air, on which I can reproduce the laggy scrolling bug reported in another thread, but scriptwriting works fine with no delay. I therefore suspect there is another factor at play.
One thing to try is to turn off spell-checking and spelling corrections via the Edit > Spelling and Grammar menu, and to turn off all auto-correction options in Scrivener’s Settings / Corrections pane. That will just tell us if it’s one of those settings causing the problem - if the problem persists, then it rules that out.
After, that, another thing to try is to go to the Settings panel, choose to save your settings to file from the “Manage…” button at the bottom (just so we have a copy of your existing settings), and then clicking the “Defaults” button and hitting “Yes” to the warning, so that all settings are reset to the defaults. Then quit Scrivener and restart (not strictly necessary, but just to clear all possible gremlins) and try again. If the bug is gone, then load the settings file you saved to disk via the “Manage…” button again and see if it returns (if so, please send us the settings file).
Next, try the test build, Build 4, that I posted here for laggy scrolling:
(Note that this build will mess up the enabled/disabled state of some buttons, as it was to test some other issues.)
Does the issue persist with that build? (I doubt the build will make a difference, but since it is testing a lag in scrolling, it’s worth checking to see if the lag here has the same cause.)
If all of that doesn’t work, then please try logging into a Guest account on your computer and testing Scrivener’s script mode there. If everything works fine there, then we know it’s something specific in your main account causing the problem.
Ha, well, I wouldn’t call it a weekend off exactly - we drove our daughter 340 miles across the country on Saturday to drop her off at university and then drove back again on Sunday. (Just for context, that’s a long way in Britain; I know it’s probably a daily commute in America. 
)
3 Likes
@KB Thanks for your help! Here’s what I found:
I followed the first two suggestions you mentioned, which were to turn off spell-checking and spelling corrections as well as all auto-correction options in the Corrections pane and there’s no typing delay now! The only downside, of course, is I can’t use tab to auto-complete scene headings, transitions, characters, etc. But the typing delay is fully gone now. I can still try all the subsequent options if you’d like just to rule out anything else that might be contributing to the issue? Let me know!
Cheers!
Great, thanks for trying that. Okay, the next thing is to go through the options you’ve turned off, and turn them on one at a time, each time turning the others off again so that only one is turned on, until you find the exact setting that is triggering the delay. Hopefully we can then narrow it down to a single setting that I can look at. I would start by turning on “Show suggestions list while typing”, as I suspect that will be the one that causes the delay to kick in again.
All the best,
Keith
1 Like
Hey KB!
And you’d be correct! Having all other settings turned off, but isolating and only turning on show suggestions list while typing is the setting that appears to be causing the issue. I hate to ask since you guys already have so much on your plate fixing all the bugs, is this something I’d have to wait for Apple to fix with the next release of Tahoe, or is this something that could be fixed in an interim/patch release of Scrivener? All the best and thank you so much for your help!
I’m not sure yet - I still need to figure out if it’s a TextKit bug or a Scrivener bug. The next thing to check:
- Open TextEdit (which you’ll find in your Applications folder). TextEdit uses Apple’s standard text system, like Scrivener.
- Create a new document.
- Go to View > Wrap to Page (this ensures that TextEdit is using the same version of the text system as Scrivener).
- Type the start of a word, e.g. “wha”.
- Hit Opt-Escape or go to Edit > Complete.
This will bring up the completions list for the part-typed word using the same mechanisms as Scrivener’s suggestions.
Do you see a delay here too, or is this fast for you?
1 Like
Hey KB,
The delay happens here in TextEdit as well upon following the instructions. Not quite as pronounced, but still present. From the looks of it, it might be an Apple bug. I tried it with several other words that were longer to autocomplete and it persisted.
Ah, yes, that seems to be a problem in Apple’s text system then, rather than anything specific to Scrivener’s code. It’s still strange that I’m not seeing it on either of my macOS 26 systems, and that does suggest that there is something specific on your machine causing the delay. If you try both TextEdit and Scrivener’s screenwriting mode in a Guest account on your machine and it works fine then, then that would suggest that it’s something specific set up in your main account.
All the best,
Keith
2 Likes
Okay, so I tried both Scrivener and TextEdit on a test/guest account without my Apple ID but unfortunately the slight delay continues even on that account. The issue wasn’t happening on while I was using Scrivener on Sequoia the same day I updated to Tahoe, so hopefully it’s something they can roll out a patch for really quickly!
Thanks once again for all your help. All the best!
Ah, that’s annoying, sorry to hear that! That definitely sounds like they’ve introduced a glitch somewhere. If you send me a video of the bug occurring in TextEdit, I’ll report it to Apple and pass on the video. (If I just send the video of the bug in Scrivener, they won’t believe it’s their fault.)
1 Like
Sounds good I’ll be sure to do that!
Best,
Sebastian
1 Like
9 posts were merged into an existing topic: How long until Scrivener is updated for macOS 26 Tahoe?
Hey Keith, sorry it’s been a while since I last replied (university’s been busy as of late ) but I downgraded to MacOS Sequoia and the tab autocomplete issue was completely non-existent on that version on the same computer where I installed Tahoe. So I reinstalled Tahoe on it again, and tried switching to Page View on TextEdit and the issue wasn’t there either. This time after this installation, the issue didn’t happen at all on TextEdit (I am running Tahoe 26.0.1, but the issue is still present in Scrivener).
What else should I try to help and narrow down the issue?
I remember you mentioning you’re not running into the issue with any of your machines running MacOS 26, which definitely points to the issue being specific on my MacBook. I’ve removed the Klack extension that makes mechanical keyboard sounds as I type completely (all files related to it).
This isn’t to invalidate the fact that it’s working on your machines, but I was wondering if it would be possible for anyone else (on the forums or on the Scrivener team) to try and replicate the issue on their machine when running macOS Tahoe? That way I can confirm it’s an issue on my machine specifically!
All the best and thanks again for your help through the process!
Can you please download and test this build, to see if helps at all?
Although I cannot reproduce your problem exactly, I have noticed that the auto-complete list is a little choppier to appear on Tahoe, which can make typing a little choppy, even if I’m not encountering a second or two delay as you are.
What I’ve done in this build is just slightly increase the delay between typing and the appearance of the completions list, from 0.05 seconds to 0.2 seconds. Let me know if that brings any improvement.
3 Likes
Keith you legend that fixed it! It doesn’t have the delay anymore!
1 Like