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
In Debugger Left and Right panel headers have the same typography as the accordion panel headers below. This makes the typographical hierarchy confusing and also ends up showing filenames in all caps for certain panels
Reproduce
Open debugger
Note typographical inconsistencies
Expected behavior
Left and Right panel headers are visually distinct from headers below, filenames are shown as-is without capitalization.
Context
Operating System and version: MacOS 12.6.3
Browser and version: Chrome version 109.0.5414.87 (Official Build) (arm64)
JupyterLab version: head-of-master (WIP 4.0.0)
The text was updated successfully, but these errors were encountered:
Alternative, use the title "Debugger" instead of the filename
Empty indicator will be needed in this case because debugger may not be enabled in specific notebooks. Currently this is indicated by "-" in place of file name which is not clear enough and users find it confusing (e.g. https://stackoverflow.com/q/75453541/6646912), we could follow blank indicator rules as suggested in #13988 (comment)
If the debugger widget is visible in the panel, its title should be "Debugger" and it should contain a placeholder to indicate that it is unavailable — see #13988 for a similar task on the TOC extension
Description
In Debugger Left and Right panel headers have the same typography as the accordion panel headers below. This makes the typographical hierarchy confusing and also ends up showing filenames in all caps for certain panels
Reproduce
Expected behavior
Left and Right panel headers are visually distinct from headers below, filenames are shown as-is without capitalization.
Context
Operating System and version: MacOS 12.6.3
Browser and version: Chrome version 109.0.5414.87 (Official Build) (arm64)
JupyterLab version: head-of-master (WIP 4.0.0)
The text was updated successfully, but these errors were encountered: