Repository navigation
[stable-0.1] fix(editor): place node text in Firefox where Chrome places it - #464
Merged
AndyScherzinger merged 1 commit intoOct 27, 2026
Merged
Conversation
The mind map nudges each node's text up or down by a fraction of the font size, taken from a table per browser and operating system that was measured years ago. Current Firefox lays out the text like Chrome, but still used its own outdated values: on Linux the text sat about a sixth of a line too high, and on Windows text in Arial or Times New Roman sat a few pixels too high. Firefox now uses Chrome's values, so text is placed the same in both browsers. Exports to PNG, SVG and PDF reuse the same text and follow along. Assisted-by: Claude Code:claude-opus-5-5 Signed-off-by: Andy Scherzinger <info@andy-scherzinger.de> (cherry picked from commit c00fb03) Signed-off-by: Andy Scherzinger <info@andy-scherzinger.de>
AndyScherzinger
added
bug
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
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.
Backport of #463, cherry-picked unchanged: the vendored kityminder-core is identical on this line.
In Firefox, node text sat too high in its box (most visibly on Linux, and on Windows for Arial and Times New Roman nodes) because Firefox still used outdated per-browser text offsets. It now uses Chrome's, so text is placed the same in both browsers. Details and checks in #463.
🤖 AI (if applicable)