Search and replace bug when using case-sensitive search

Hey Balsamiq gang,

I once said “If I won a billion dollars, I would buy Balsamiq and make them implement search and replace”. So it goes without saying that I’m enjoying this feature. :slight_smile:

I have found one bug. When searching and replacing in “exact match” mode, occasionally the “find” text is not replaced; instead, the “replace with” text is appended to it. Oddly, this seems to happen almost entirely inside Comment (yellow sticky note) containers. It may have something to do with the text being adjacent to a period. For example, if searching for “one” and replacing with “two”, I occasionally get a result of “onetwo”. It seems that once I searched for “one” and it replaced an instance of “one.” with “one.two”, but I may not remember that correctly.

Anyway, hope this helps!

Woof, that’s a good one, Roger.

I’m trying to reproduce it on my end, and I’m having trouble. Can you tell me what browser and OS you’re running?

Windows 11 and Firefox.

Sorry, Roger, I didn’t mean to make you think we forgot about this, my friend.

I’ve been testing and I still cannot reproduce. Would you be able to share a project with me? You can email it to

We will get to the bottom of this.

Sure - I’ll be glad to. Thanks again, Brendan.

1 Like