You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I can partially reproduce this on Debian Unstable (DE: Plasma on Wayland).
Attempting to use the browser search in a sketch with an error does correctly open the search page in my default browser.
However, attempting the browser search without an error results in the search page opening with the ++++++++++... string as the search query.
So the issue with the browser search not opening seems to be an issue with the MacOS implementation specifically, which I don't have the means to tackle, or at least not a Linux implementation issue. I have tracked down the + bug though.
The +++++++... spam originates with Editor.statusEmpty(), which "clears" the EditorStatus message by setting it to Editor.EMPTY, which is actually about ~200 space characters. This spacer string gets URL-encoded into those ~200 + characters before going into Platform.openURL in the EditorStatus mouseReleased handler.
EditorStatus has an empty() method which seems to properly clear the status message to an actual empty string. Replacing statusNotice(EMPTY) with this status.empty() in Editor.statusEmpty() seems to be the correct way to fix this, and has the additional effect of causing the copy-status-to-clipboard/search-for-error button to be hidden when there's no errors in the sketch, which seems to be the intended behavior.
Here's a side-by-side of the current statusNotice(EMPTY) behavior on the left and the status.empty() behavior on the right - Sorry for the horrendous quality, KolourPaint is apparently terrible for cropping screenshots. The console text on the right is just some trace output.
Activity
aj-m commentedon Jul 10, 2025
I can partially reproduce this on Debian Unstable (DE: Plasma on Wayland).
Attempting to use the browser search in a sketch with an error does correctly open the search page in my default browser.
However, attempting the browser search without an error results in the search page opening with the
++++++++++...string as the search query.So the issue with the browser search not opening seems to be an issue with the MacOS implementation specifically, which I don't have the means to tackle, or at least not a Linux implementation issue. I have tracked down the
+bug though.The
+++++++...spam originates withEditor.statusEmpty(), which "clears" the EditorStatus message by setting it to Editor.EMPTY, which is actually about ~200 space characters. This spacer string gets URL-encoded into those ~200+characters before going intoPlatform.openURLin the EditorStatusmouseReleasedhandler.processing4/app/src/processing/app/ui/Editor.java
Lines 91 to 94 in b8c0857
processing4/app/src/processing/app/ui/Editor.java
Lines 2664 to 2669 in b8c0857
processing4/app/src/processing/app/ui/EditorStatus.java
Lines 135 to 147 in b8c0857
EditorStatus has an
empty()method which seems to properly clear the status message to an actual empty string. ReplacingstatusNotice(EMPTY)with thisstatus.empty()inEditor.statusEmpty()seems to be the correct way to fix this, and has the additional effect of causing the copy-status-to-clipboard/search-for-error button to be hidden when there's no errors in the sketch, which seems to be the intended behavior.processing4/app/src/processing/app/ui/EditorStatus.java
Lines 306 to 311 in b8c0857
processing4/app/src/processing/app/ui/EditorStatus.java
Lines 417 to 424 in b8c0857
Here's a side-by-side of the current
statusNotice(EMPTY)behavior on the left and thestatus.empty()behavior on the right - Sorry for the horrendous quality, KolourPaint is apparently terrible for cropping screenshots. The console text on the right is just some trace output.SableRaf commentedon Jul 10, 2025
Thanks so much for taking the time to investigate this and share such a clear and detailed explanation. I really appreciate it.
I tried out your suggested fix, and it does seem to solve the
+++++++...issue on macOS as well.If you're up for it, I’d be glad to see you open a PR with the fix. Thanks @aj-m ✨
Properly clear EditorStatus.message with empty()