Version Strings should not be compared against Numbers. For example, the version "1.20" is greater than "1.2" and less than "1.200", but as Numbers, they are all 1.2.

Pass in one of the browser versions: SC.browser.version, SC.browser.engineVersion or SC.browser.osVersion and a String to compare against. The function will split each version on the decimals and compare the parts numerically.

Examples:

SC.browser.compare('1.20', '1.2') == 18 SC.browser.compare('1.08', '1.8') == 0 SC.browser.compare('1.1.1', '1.1.004') == -3

This method returns safe CSS attribute names for current and future browsers.

Using browser specific CSS prefixes is a risky coding practice. With sufficient testing, you may be able to match attributes across today's most popular browsers, but this is a lot of work and not future proof. For instance, if a browser drops the prefix and supports the standard CSS name, your code will suddenly stop working. This happens ALL the time!

Instead, use SC.browser.experimentalCSSNameFor(standardCSSName), which will test support for the standard CSS name and if not found will try the prefixed version with the current browser's prefix appended.

Note: the proper CSS name is only determined once per standard CSS name tested and then cached. Therefore, calling experimentalCSSNameFor repeatedly has no performance detriment.

For example,

var boxShadowCSS = SC.browser.experimentalCSSNameFor('box-shadow'),
  el = document.createElement('div');

// `boxShadowCSS` may be "box-shadow", "-webkit-box-shadow", "-ms-box-shadow", etc. depending on the current browser.
el.style.cssText = boxShadowCSS + " rgb(0,0,0) 0px 3px 5px";

Improving deduction

Occasionally a browser will appear to support a style, but will fail to actually accept a value. In order to ensure that the style doesn't just exist but is also usable, you can provide an optional testValue that will be used to verify that the detected style is usable.

This simple method allows you to more safely use experimental properties and methods in current and future browsers.

Using browser specific methods and properties is a risky coding practice. With sufficient testing, you may be able to match prefixes to today's browsers, but this is prone to error and not future proof. For instance, if a property becomes standard and the browser drops the prefix, your code could suddenly stop working.

Instead, use SC.browser.experimentalNameFor(target, standardName), which will check the existence of the standard name on the target and if not found will try different camel-cased versions of the name with the current browser's prefix appended.

If it is still not found, SC.UNSUPPORTED will be returned, allowing you a chance to recover from the lack of browser support.

Note that experimentalNameFor is not really meant for determining browser support, only to ensure that using browser prefixed properties and methods is safe. Instead, SC.platform provides several properties that can be used to determine support for a certain platform feature, which should be used before calling experimentalNameFor to safely use the feature.

For example,

// Checks for IndexedDB support first on the current platform.
if (SC.platform.supportsIndexedDB) {
  var db = window.indexedDB,
    // Example return values: 'getDatabaseNames', 'webkitGetDatabaseNames', 'MozGetDatabaseNames', SC.UNSUPPORTED.
    getNamesMethod = SC.browser.experimentalNameFor(db, 'getDatabaseNames'),
    names;

    if (getNamesMethod === SC.UNSUPPORTED) {
      // Work without it.
    } else {
      names = db[getNamesMethod](...);
    }
} else {
  // Work without it.
}

Improving deduction

Occasionally a target will appear to support a property, but will fail to actually accept a value. In order to ensure that the property doesn't just exist but is also usable, you can provide an optional testValue that will be temporarily assigned to the target to verify that the detected property is usable.

This method returns safe style names for current and future browsers.

Using browser specific style prefixes is a risky coding practice. With sufficient testing, you may be able to match styles across today's most popular browsers, but this is a lot of work and not future proof. For instance, if a browser drops the prefix and supports the standard style name, your code will suddenly stop working. This happens ALL the time!

Instead, use SC.browser.experimentalStyleNameFor(standardStyleName), which will test support for the standard style name and if not found will try the prefixed version with the current browser's prefix appended.

Note: the proper style name is only determined once per standard style name tested and then cached. Therefore, calling experimentalStyleNameFor repeatedly has no performance detriment.

For example,

var boxShadowName = SC.browser.experimentalStyleNameFor('boxShadow'),
  el = document.createElement('div');

// `boxShadowName` may be "boxShadow", "WebkitBoxShadow", "msBoxShadow", etc. depending on the browser support.
el.style[boxShadowName] = "rgb(0,0,0) 0px 3px 5px";

Improving deduction

Occasionally a browser will appear to support a style, but will fail to actually accept a value. In order to ensure that the style doesn't just exist but is also usable, you can provide an optional testValue that will be used to verify that the detected style is usable.