Skip to content

fix: update font scaling logic to not use hard coded values #264

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
Mar 10, 2025

Conversation

andrewrobinsonhodges-snyk
Copy link
Contributor

Description

Provide description of this PR and changes, if linked Jira ticket doesn't cover it in full.

Checklist

  • Tests added and all succeed
  • Linted
  • CHANGELOG.md updated
  • README.md updated, if user-facing

Screenshots / GIFs

Visuals that may help the reviewer. Please add screenshots for any UI change. GIFs are most welcome!

@andrewrobinsonhodges-snyk andrewrobinsonhodges-snyk requested a review from a team as a code owner March 6, 2025 16:19

// FontRegistry uses pt sizes, not px, so we convert here, using standard web values from
// https://www.w3.org/TR/css3-values/#absolute-lengths
double pxToPtMultiplier = 72.0 / 96.0;
Copy link
Contributor

@bastiandoetsch bastiandoetsch Mar 10, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess it would make sense to define this as a constant.

@andrewrobinsonhodges-snyk andrewrobinsonhodges-snyk merged commit 50ea458 into main Mar 10, 2025
8 checks passed
@andrewrobinsonhodges-snyk andrewrobinsonhodges-snyk deleted the fix/scan-summary-font-scaling branch March 10, 2025 12:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants