Conversation
Port the symbol-palette v2 feature (rail-based palette + user-customizable categories/symbols in localStorage) from the ext-ce fork (commit bee34ec 'Initial files') into the current CE tree, adapted to the modern ide-react architecture: - add services/web/modules/symbol-palette (components, config context, default symbol data, categories util, safe character helper) - register sourceEditorSymbolPalette / settingsEntries / railEntries module imports and add 'symbol-palette' to moduleImportSequence (Features gate -> ol-symbolPaletteAvailable meta -> toolbar command) - move the palette out of the editor bottom PanelGroup into a rail tab; toolbar 'Symbol' command opens the rail tab via ui:select-rail-tab - add moduleSettingsEntries spread to the settings modal - append rail-panel + settings page styles to symbol-palette.scss - add en + extracted i18n keys for the settings UI Audit fixes vs the ported source: - safe symbol character derivation (U+CUSTOM-*/non-hex codepoints no longer yield NaN/garbage chars or throw RangeError) - validate + sanitize + dedupe imported palette configs; addSymbol now guarantees unique codepoints (the identity key) - re-select active category in settings when it disappears (import/reset) - remove dead code (unused state/imports, orphan close-button component, unused buildCategorisedSymbols), fix window globals for lint - fix scss append seam and overflow shorthand; resolve the editor-context SymbolWithCharacter import with a type-only shim
Bake the contents of the compose-local settings.js.fixed override into server-ce/config/settings.js (Dockerfile already copies it to /etc/overleaf/settings.js), so the image no longer needs the ./settings.js.fixed volume mount: - SMTP: OVERLEAF_EMAIL_SMTP_PASS_FILE support (pass read from file), takes precedence over OVERLEAF_EMAIL_SMTP_PASS - enableRegiserPage: OVERLEAF_ENABLE_REGISTER_PAGE flag
… subpath User test feedback fixes: - symbol palette header was ugly when the rail panel is narrow: switch .symbol-palette-header to a column layout (horizontal scrolling tab row on top, full-width search below) instead of a wrapping row - settings page had two intersecting scrollbars: remove the inner .sp-settings-table-container scroll (max-height/overflow) so the settings modal's own scroll is the only one (table header still sticks to the modal scroll) - drop the dead sourceEditorSymbolPalette registration + symbol-palette.js subpath: the palette is served by the rail entry (panel) and the settings entry; nothing renders the pane anymore
…pping - The palette root used min-content sizing, so when the rail panel was resized the panel width and the internal content fought each other in an endless re-layout loop: the editor pane kept re-measuring (text and scrollbar flickering for minutes after the drag). Break the loop by making the palette content width-independent of the panel width: contain: layout paint on .symbol-palette-rail-panel and min-width: 0 down the whole flex chain (panel body, container, palette, body, items, search) - Restore the requested dynamic line-wrap on the category tabs (flex-wrap: wrap) instead of a horizontal scroll row, so the tab header grows vertically instead of fighting the panel width
…ight Root cause of the persistent 'Measure loop restarted' / text + scrollbar flicker after palette resize: removing the old bottom PanelGroup left .ide-redesign-editor-content (flex: 1 1 auto, default min-height: auto) growing to its content height (multi-megapixel). That made .cm-scroller unbounded, so the vertical-overflow bottom-padding plugin (padding = scroller clientHeight - line height) fed its own output back in on every geometry change: a never-converging positive-feedback loop that resized the editor and re-measured CodeMirror continuously. Fix: bound the editor content box (min-height: 0 + overflow hidden on .ide-redesign-editor-content) so the cm chain always has a definite viewport height; the padding plugin then converges in one pass. Also: give the breadcrumb bar a little more height (28px -> 34px) as requested.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
I call upon on all gods who are responsible to UI / UX, please update the crusty symbol palette in overleaf.com. I would like to improve the symbol palette downstream but compability issues (means opinions) with overleaf.com are blocking me. Use the code however you want, you don't need to disclose it and you don't need to add it to overleaf CE (I know that otherwise it is a total block for you).
Related issues / Pull Requests
Contributor Agreement
This is human guided AI (mainly qwen3.8; a bit of VS code copilot AI code might be left) and hence can not be copyrighted. You can do with the code what what ever you want. This includes including (& modify) the code into overleaf.com and other closed source projects without the need to disclose the code.