Skip to content
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

fix(embedded-webfonts): retrieving font family via getPropertyValue #507

Open
wants to merge 2 commits into
base: master
Choose a base branch
from

Conversation

petrmiko
Copy link

@petrmiko petrmiko commented Feb 25, 2025

Description

Motivation and Context

Current solution attempts to read fontFamily property from style, which is a https://developer.mozilla.org/en-US/docs/Web/API/CSSStyleDeclaration instance, and results in an undefined font that later crashes in normalizeFontFamily. This fix leverages CSSStyleDeclaration.getPropertyValue() and provides empty string in case of a node not having defined font-family.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Enhancement (changes that improvement of current feature or performance)
  • Refactoring (changes that neither fixes a bug nor adds a feature)
  • Test Case (changes that add missing tests or correct existing tests)
  • Code style optimization (changes that do not affect the meaning of the code)
  • Docs (changes that only update documentation)
  • Chore (changes that don't modify src or test files)

Self Check before Merge

  • My code follows the code style of this project.
  • My change requires a change to the documentation.
  • I have updated the documentation accordingly.
  • I have read the CONTRIBUTING document.
  • I have added tests to cover my changes.
  • All new and existing tests passed.

@biiibooo
Copy link
Contributor

biiibooo bot commented Feb 25, 2025

👋 @petrmiko

💖 Thanks for opening this pull request! 💖

Please follow the contributing guidelines. And we use semantic commit messages to streamline the release process.

Examples of commit messages with semantic prefixes:

  • fix: don't overwrite prevent_default if default wasn't prevented
  • feat: add graph.scale() method
  • docs: graph.getShortestPath is now available

Things that will help get your PR across the finish line:

  • Follow the TypeScript coding style.
  • Run npm run lint locally to catch formatting errors earlier.
  • Document any user-facing changes you've made.
  • Include tests when adding/changing behavior.
  • Include screenshots and animated GIFs whenever possible.

We get a lot of pull requests on this repo, so please be patient and we will get back to you as soon as we can.

Copy link

codecov bot commented Feb 25, 2025

Codecov Report

Attention: Patch coverage is 66.66667% with 1 line in your changes missing coverage. Please review.

Project coverage is 66.50%. Comparing base (d9b2fcf) to head (746b875).
Report is 1 commits behind head on master.

Files with missing lines Patch % Lines
src/embed-webfonts.ts 66.66% 0 Missing and 1 partial ⚠️
Additional details and impacted files
@@           Coverage Diff           @@
##           master     #507   +/-   ##
=======================================
  Coverage   66.50%   66.50%           
=======================================
  Files          10       10           
  Lines         612      612           
  Branches      150      150           
=======================================
  Hits          407      407           
  Misses        144      144           
  Partials       61       61           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@cheungpat
Copy link

cheungpat commented Feb 27, 2025

Since v1.11.12, the problem causes an error when using Firefox to save html to image when a css webfont is used. For Firefox, the solution is to pin to 1.11.11.

I believe this PR fixes the problem. Somehow the github action failed to label the PR.

refs #476

@tuhm1
Copy link
Contributor

tuhm1 commented Mar 2, 2025

So apparently in Firefox we must use getPropertyValue to access property values of CSSStyleRule.

I apologize for causing the issue.

Btw, I think normalizeFontFamily doesn't need to handle undefined because getPropertyValue always returns a string (empty string if not set).

This will fix: #508

@petrmiko petrmiko changed the title fix: retrieving font family via getPropertyValue, accounting for missing font family fix(embedded-webfonts): retrieving font family via getPropertyValue Mar 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants