I have a lot of web-addresses as snippets. About 20% of the time the URL is expanded with the first character of the snippet put in front of htt…, to which Safari reacts with an error of course.
Years ago I filed a bug report on this and got a reply that this was due to Safari and there was nothing the developers could do to remedy this.
Now it is 2025 and I wonder if there is really nothing we can do to make this better.
Are other folks experiencing the same?
Hi Thomas, welcome! We have the product and support teams looking into this now. For what it’s worth, I can replicate this issue consistently in Safari.

Hey Thomas, I just realized that I was getting the extra character at the end of the URL, and you’re getting it at the beginning.
Just to make sure we’re seeing the same thing, can you provide me:
- The version of TextExpander you’re using?
- The version of Safair you’re using?
You can check to see which version of TextExpander you’re on by going to ‘TextExpander’ in your menu bar (whilst TextExpander is open and focused), then selecting “About TextExpander” as shown here:
The instructions are the same for Safari, except you choose Safari > About Safari.
short answer: all the latest versions, always
Safari 18.4 (20621.1.15.11.10)
TE 8.2.5. (825.2)
macOS 15.4.1 (24E263) · MacBookPro M2
PS: Note to developers:
Please make Version info in About… box copyable! It is not as of this writing, no way to mark it.
PS: Note to webadmin:
Please make this textbox expandable! Thanks!
Hey Thomas, you can make the post editor larger by either clicking and dragging the drag handle in the center or by clicking the fullscreen icon on the right.
Thank you, it works! I was looking for the resize-symbol on the lower right corner.
1 Like
Hey, we accomplished that much at least! The product team is investigating a bugfix for the Safari issue and also exploring making the version information copyable.
1 Like
Hello @josh.centers
I want to inform you that this has also been happening to me on Google Chrome. Whenever I expand snippets, the first character was put in the front of the URL.
Hope we can have a fix for this soon.
Hi @AllanJoseph_Dela_Pen! Can you answer a couple of clarifying questions?
- Are you using the desktop client or the Chrome extension? If it’s the desktop client, are you Mac or Windows?
- Are you running the Chrome extension alongside a desktop client?
Hey, for everyone experiencing this on the desktop client, can you please update to 8.4 and let us know if this is still happening?
I am on Version: 8.4.1b1 (841.1) – BTW: Please make this copyable in the about-box.
It still happens at the usual rate.
1 Like