Permalink
Commits on Jan 10, 2012
  1. Release 1.0.24

    Sean McBride committed Jan 10, 2012
  2. Merge pull request #41 from typekit/webkit_workaround_refinement

    Webkit workaround refinement
    Sean McBride committed Jan 10, 2012
Commits on Jan 6, 2012
  1. Untabified the file.

    jeremiele committed Jan 6, 2012
Commits on Jan 3, 2012
  1. Change the order in which we return the sizes since the setup of the …

    …last
    
    resort font moved.
    jeremiele committed Jan 3, 2012
  2. Revert "Fixed/Updated tests."

    This reverts commit 2a889a5.
    jeremiele committed Jan 3, 2012
  3. Fixed/Updated tests.

    jeremiele committed Jan 3, 2012
  4. Refine the comment.

    jeremiele committed Jan 3, 2012
  5. Always set our test string.

    jeremiele committed Jan 3, 2012
Commits on Dec 5, 2011
  1. Work around another strange webkit behavior, when getting the size of

    the span for a weight different than 400 the browser sometimes return the
    size of the 400 weight. Also when the size change for the first time on webkit
    remove every other value from the last resort size set and only keep that one
    value, in case the final size could match one of the other size in the set.
    jeremiele committed Dec 5, 2011
Commits on Nov 29, 2011
  1. Release 1.0.23

    Sean McBride committed Nov 29, 2011
  2. Merge pull request #39 from typekit/webkit_fix_inheritance

    Webkit fix inheritance
    Sean McBride committed Nov 29, 2011
  3. Merge pull request #37 from ahume/fontdeck_api_v2

    Fontdeck module - small change
    Sean McBride committed Nov 29, 2011
  4. Moved the LastResortWebKitFontWatchRunner under the google module bec…

    …ause
    
    we now have a special case for fonts that we know are metrics compatible
    with default system fonts. This is far from being perfect, but should work
    until the WebKit bug is fixed.
    jeremiele committed Nov 29, 2011
  5. Added tests for LastResortWebKitFontWatchRunner and updated tests

    for FontWatcher and FontWatcherRunner.
    jeremiele committed Nov 29, 2011
  6. Revert "Cleanup super ctor code, just call base class directly."

    This reverts commit 6a3dee2.
    
    Revert this change to avoid Closure compiler warning.
    jeremiele committed Nov 29, 2011
Commits on Nov 18, 2011
Commits on Nov 9, 2011
Commits on Jul 1, 2011
  1. Release 1.0.22

    Sean McBride committed Jul 1, 2011
  2. Merge pull request #32 from typekit/fix-rendering-false-positive

    Fix rendering false positive
    Sean McBride committed Jul 1, 2011
Commits on Jun 27, 2011
  1. Fix indentation

    Sean McBride committed Jun 27, 2011
  2. Clarify comments in the test

    Sean McBride committed Jun 27, 2011
Commits on Jun 24, 2011
  1. Speed up font watching loop for checking test spans

    The original value was somewhat arbitrary and some browsers can do the check
    faster than this if we set the timeout faster. This is still probably slow
    enough not to put undue burden on browsers and it negates any speed loss from
    the previous change of needing to see a new size twice before we trigger
    active.
    Sean McBride committed Jun 24, 2011
Commits on Jun 17, 2011
  1. Release 1.0.21

    Sean McBride committed Jun 17, 2011
  2. Merge pull request #31 from bee525/patch-1

    changed api to use https if coming from secure site.
    Sean McBride committed Jun 17, 2011
Commits on Mar 30, 2011
  1. Release 1.0.20

    Sean McBride committed Mar 30, 2011
Commits on Mar 28, 2011
  1. Improve positioning CSS for fontwatcher spans

    Fontwatcher spans are appended to the body and positioned absolutely offscreen
    so that they don't affect the rendering of the page. Before, their top was set
    to -999px, but the left position was not set. This means that the horizontal
    position of each span was unchanged from what it would have been if it was
    still in the document's flow.
    
    Normally, this wasn't a problem, but if the user's page ends with inline or
    floated elements, the horizontal position of these spans can be pushed to the
    right and they can cause a horizontal scrollbar to appear temporarily on the
    page while the fonts are loading.
    
    Explicitly setting the left position to a negative value makes the positioning
    of the font watcher spans totally deterministic and should ensure that
    scrollbars never appear, no matter what markup or CSS the user places on the
    page.
    Sean McBride committed Mar 28, 2011