Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
Trac
Trac
  • Project overview
    • Project overview
    • Details
    • Activity
  • Issues 246
    • Issues 246
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Operations
    • Operations
    • Metrics
    • Incidents
  • Analytics
    • Analytics
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Create a new issue
  • Issue Boards

GitLab is used only for code review, issue tracking and project management. Canonical locations for source code are still https://gitweb.torproject.org/ https://git.torproject.org/ and git-rw.torproject.org.

  • Legacy
  • TracTrac
  • Issues
  • #8770

Closed (moved)
Open
Opened Apr 25, 2013 by Mike Perry@mikeperry

Verify that @font-face fallback fonts can't be probed

In #8455 (closed), I disabled the local fallback rendering for @font-face. I did not attempt to disable all of the code that handles cases where WebFonts weren't downloaded yet, because I was hesitant to introduce bugs, especially without a test case to verify that what I disabled was actually relevant to font probing.

However, there did appear to be sections of the code that at least internally allowed Firefox to estimate font sizes before the webfont completed loading. It was not immediately clear to me if these estimations were available to content or not, and which fonts they were based on.

If they are available, it would be very useful to have a test case to verify against as I try removing/altering some of those codepaths.

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: legacy/trac#8770