Skip to content
Commits on Sep 11, 2012
  1. Release 1.0.31

    Sean McBride committed Sep 11, 2012
  2. Merge pull request #62 from typekit/improve_weight_style_parsing

    Changed the way the variation is parsed to properly handle every variation
    Sean McBride committed Sep 11, 2012
Commits on Sep 7, 2012
  1. @jeremiele
Commits on Aug 17, 2012
  1. Release 1.0.30

    Sean McBride committed Aug 17, 2012
  2. Merge pull request #60 from cbosco/global_options

    Global options
    Sean McBride committed Aug 17, 2012
  3. Merge pull request #61 from typekit/windows-phone

    Recognize Windows Phone 8 devices correctly
    Sean McBride committed Aug 17, 2012
Commits on Aug 15, 2012
  1. Make sure we can detect that old versions of win phone don't support …

    …fonts
    Sean McBride committed Aug 14, 2012
Commits on Aug 14, 2012
  1. Add the ability to detect Windows Phone devices

    Sean McBride committed Aug 14, 2012
Commits on Aug 8, 2012
  1. Create globalNamespaceObject variable for easy namespacing in initial…

    …ize.js
    Chris Bosco committed Aug 8, 2012
  2. Replace string literal 'WebFont' global with the globalName variable …

    …from initialize.js
    Chris Bosco committed Aug 8, 2012
Commits on Jul 26, 2012
  1. Release 1.0.29

    Sean McBride committed Jul 26, 2012
  2. Merge pull request #58 from typekit/fallback_fonts_scaleback

    Fallback fonts scaleback
    Sean McBride committed Jul 26, 2012
  3. Merge pull request #57 from typekit/urlbuilder_cleanup

    Updated FontApiUrlBuilder to properly take into account empty variations...
    Sean McBride committed Jul 26, 2012
  4. Merge pull request #56 from typekit/sm-mobile-browser-support

    Additional mobile browser detection
    Sean McBride committed Jul 26, 2012
Commits on Jul 25, 2012
  1. Ensure that Opera Mini is NOT detected as supporting web fonts

    While Opera Mobile supports web fonts and is like a mobile version of full
    desktop Opera, the Opera Mini application doesn't currently support web fonts
    and also follows a different versioning system separate from the main Opera
    version. Thus, we should treat Opera Mini as a separate browser for the
    purposes of web font support, and make sure that we don't return false
    positives for support as well.
    Sean McBride committed Jul 25, 2012
  2. Add a user agent test for Opera Mobile on Android

    Sean McBride committed Jul 25, 2012
Commits on Jul 18, 2012
  1. @jeremiele
  2. @jeremiele
Commits on Jul 17, 2012
Commits on Jun 4, 2012
  1. Release 1.0.28

    Sean McBride committed Jun 4, 2012
  2. Merge pull request #52 from typekit/chrome-os-support

    Add support for detecting Chrome OS with the user agent parser
    Sean McBride committed Jun 4, 2012
Commits on May 24, 2012
Commits on Apr 20, 2012
  1. Release 1.0.27

    Sean McBride committed Apr 20, 2012
  2. Merge pull request #50 from typekit/sm-domhelper-update

    Remove UserAgent from DomHelper, replace with feature detection
    Sean McBride committed Apr 20, 2012
Commits on Apr 19, 2012
  1. Add an additional test for the feature detection behavior

    Sean McBride committed Apr 18, 2012
  2. Fix type union syntax for Closure compiler

    Sean McBride committed Apr 18, 2012
  3. Use a "feature detect on first call" style to avoid constructor DOM

    This is a less onerous way to avoid DOM construction caused by the DomHelper
    constructor. We make a method to check if a feature is supported and memoize
    the value the first time it's called.
    Sean McBride committed Apr 18, 2012
  4. Move feature detection out of the constructor

    Otherwise, the JS can't run in environments that don't have a DOM
    implementation, which makes things difficult.
    Sean McBride committed Apr 18, 2012
Commits on Apr 18, 2012
  1. Remove UserAgent from DomHelper, replace with feature detection

    UserAgent was required to construct a DomHelper, but the only thing it was
    used for is in setStyle to determine if we're in an old IE and need to use a
    different approach. I was using DomHelper in some code and finding it cumbersome
    to have a UserAgent instance around as well. This goal is better accomplished
    with a feature-detection approach anyway.
    
    I've replaced the UserAgent arg with feature detection for getting/setting the
    style attribute. This is a very similar approach to the one that jQuery uses to
    detect the same feature.
    
    This has the added side-effect of allowing many of the modules to no longer
    construct a UserAgent instance using the parser, since they only used it for the
    DomHelper, which simplifies things.
    Sean McBride committed Apr 18, 2012
Commits on Feb 15, 2012
  1. Release 1.0.26

    Sean McBride committed Feb 15, 2012
  2. Merge pull request #47 from typekit/compiler_update

    Compiler update
    Sean McBride committed Feb 15, 2012
  3. @jeremiele

    Fixed js compiler warnings.

    jeremiele committed Feb 15, 2012
  4. @jeremiele

    Updated js compiler and Rakefile since the output_wrapper_marker flag…

    … has been removed. Since we were using the default marker anyway removing this flag is not an issue.
    jeremiele committed Feb 15, 2012
  5. Merge pull request #46 from typekit/plus_sign_in_family

    Updated the Google Web Fonts API parser to accept family names with a plus sign
    Sean McBride committed Feb 14, 2012
Something went wrong with that request. Please try again.