I filed a bug report in github but the github-actions bot keeps marking the bug report as stale

Support
1

Operating system

Linux

Joplin version

3.6.15

Desktop version info

Joplin 3.6.15 (prod, linux)

Device: linux, AMD Ryzen 7 9700X 8-Core Processor
Client ID: 497850b832674c438eead8bd21dd2672
Sync Version: 3
Profile Version: 49
Keychain Supported: No
Alternative instance ID: -
Sync target: (None)
Editor: Rich Text

Revision: c615726

Backup: 1.5.1
Freehand Drawing: 4.3.0

Editor

Rich Text Editor

What issue do you have?

There is a bug where the find function doesn't find text that is in code blocks when you search with the rich text editor but finds the same text immediately in code blocks if you use find with the markdown editor instead

I made a post here since May:

But my report keeps getting marked as "stale" by the automated github bot:
"This issue may be closed if no further activity occurs. You may comment on the issue and I will leave it open. Thank you for your contributions."

I have also provided screenshots there as well. The bot suggested posting in the Joplin forums, so here I am.

2

It looks like there's already multiple bug reports for this, these ones are tagged/triaged already so they don't get marked as stale:

And it seems to be an upstream bug with TinyMCE: Search doesn't match results for text inside the "code" inline styles · Issue #6966 · tinymce/tinymce · GitHub

3

Thank you for the reply and the explanation! I appreciate it.

So does this mean that this issue cannot be resolved from Joplin, it has to be solved upstream from TinyMCE?

The bug report for TinyMCE is from 2021, does that mean the chances of this getting fixed are very slim to none? :frowning:

Can a different program other than TinyMCE be used, is there anything that can be done alternatively from Joplin's side?

4

TinyMCE editor will be replaced at some point, with the same rich text editor used on mobile. But I don't know the timeline for that unfortunately

5

oh so there are already plans to replace it then? that's good news I guess if it will fix the problem.

Hopefully it will be done sooner rather than later especially if it makes the mobile and desktop versions more similar that sounds like a win to me. (It will be easier to maintain too)