Project
ide
Description
The Add Data Breakpoint form inside the debugger panel (src/components/debugger/DataBreakpointPanel.tsx, lines 123 and 139) applies color: var(--text-base) to both the variable name text input and the access type select dropdown. In the design token system, --text-base is defined as 14px in design-tokens.css — a font-size value, not a color. Both declarations are invalid CSS and the browser silently discards them. As a result, text typed into the variable name field and the selected option label in the access type dropdown inherit their foreground color from surrounding ancestors rather than the intended theme value. A third instance of the same invalid token appears conditionally at line 205 on the enabled breakpoint name span, meaning the breakpoint list is also affected when entries are active.
Error Message
Debug Logs
System Information
Cortex IDE: v1.1.0
OS: Ubuntu 25.04
CPU: 13th Gen Intel Core i7-13650HX
RAM: 15 GB total
Screenshots
Steps to Reproduce
Open Cortex IDE and navigate to the Run & Debug panel.
Expand the Data Breakpoints section.
Click the + button to open the Add Data Breakpoint form.
The variable name (line 123) and the access type (line 139) are now visible.
Open DevTools → Elements and inspect each form control.
Check the computed color value on both elements.
Expected Behavior
Text typed into the variable name field and the option label shown in the access type dropdown should render in the primary text color defined by the active theme (--cortex-text-primary). Both inputs should be clearly legible against their var(--surface-sunken) backgrounds in all themes.
Actual Behavior
color: var(--text-base) resolves to 14px on both the and the , so the browser drops the declarations. Both controls inherit a foreground color from an ancestor element, which is theme-dependent and not guaranteed to have adequate contrast against the sunken surface background. In certain themes the typed expression and the selected access type option can become difficult to read. Enabled breakpoints in the list below also show the same issue via the conditional at line 205, where the active variable name falls back to an inherited color rather than the intended primary text.
Additional Context
No response
Project
ide
Description
The Add Data Breakpoint form inside the debugger panel (src/components/debugger/DataBreakpointPanel.tsx, lines 123 and 139) applies color: var(--text-base) to both the variable name text input and the access type select dropdown. In the design token system, --text-base is defined as 14px in design-tokens.css — a font-size value, not a color. Both declarations are invalid CSS and the browser silently discards them. As a result, text typed into the variable name field and the selected option label in the access type dropdown inherit their foreground color from surrounding ancestors rather than the intended theme value. A third instance of the same invalid token appears conditionally at line 205 on the enabled breakpoint name span, meaning the breakpoint list is also affected when entries are active.
Error Message
Debug Logs
System Information
Screenshots
Steps to Reproduce
Open Cortex IDE and navigate to the Run & Debug panel.
Expand the Data Breakpoints section.
Click the + button to open the Add Data Breakpoint form.
The variable name (line 123) and the access type (line 139) are now visible. Open DevTools → Elements and inspect each form control. Check the computed color value on both elements. Expected Behavior Text typed into the variable name field and the option label shown in the access type dropdown should render in the primary text color defined by the active theme (--cortex-text-primary). Both inputs should be clearly legible against their var(--surface-sunken) backgrounds in all themes. Actual Behavior color: var(--text-base) resolves to 14px on both the and the , so the browser drops the declarations. Both controls inherit a foreground color from an ancestor element, which is theme-dependent and not guaranteed to have adequate contrast against the sunken surface background. In certain themes the typed expression and the selected access type option can become difficult to read. Enabled breakpoints in the list below also show the same issue via the conditional at line 205, where the active variable name falls back to an inherited color rather than the intended primary text. Additional Context No response