Open
Description
Describe the problem
When using the "Light High Contrast" IDE UI theme, no highlight is visible for text selected in the "Serial Monitor" view.
To reproduce
- Select File > Preferences... (or Arduino IDE > Settings... for macOS users) from the Arduino IDE menus.
- Select "Light" from the "Theme" menu.
- Click the "OK" button.
- Upload any sketch that produces serial output:
void setup() { Serial.begin(9600); while (!Serial) {} delay(200); Serial.println("The original machine had a base-plate of prefabulated aluminite, surmounted by a\n malleable logarithmic casing in such a way that the two main spurving bearings\n were in a direct line with the pentametric fan. The latter consisted simply of\n six hydrocoptic marzlevanes, so fitted to the ambifacient lunar waneshaft that\n side fumbling was effectively prevented. The main winding was of the normal\n lotus-o-delta type placed in panendermic semi-bovoid slots in the stator, every\n seventh conductor being connected by a non-reversible tremie pipe to the\n differential girdlespring on the \"up\" end of the grammeters."); } void loop() {}
- Open the "Serial Monitor" view.
- Click and drag the mouse pointer across the text in the "Serial Monitor" view.
🙂 The selected text is highlighted by a contrasting background color:
- Select File > Preferences... (or Arduino IDE > Settings... for macOS users) from the Arduino IDE menus.
- Select "Light High Contrast" from the "Theme" menu.
- Click the "OK" button.
🐛 There is no highlight on the selected text:
Expected behavior
Text selected in "Serial Monitor" is highlighted in some way regardless of which supported theme is selected.
Arduino IDE version
Operating system
- macOS
- Windows
Operating system version
- macOS Sonoma 14.0 (23A344)
- Windows 11
Additional context
Same behavior in:
arduino-ide_nightly-20230804_macOS_64bit
and Arduino IDE 2.2.1
The low level functionality of the highlight works fine even though it is not visible. You can copy the invisibly highlighted text to the clipboard as usual.
Issue checklist
- I searched for previous reports in the issue tracker
- I verified the problem still occurs when using the latest nightly build
- My report contains all necessary details