joehe_cn
joehe_cn

1-2 Release notes 发行说明

layout: default
type: about
shortname: Docs
title: Release notes
subtitle: About this release

{% include toc.html %}

Release 1.2.3 (2015-11-16)

This release fixes the following issues:

  • Fixes #2381,
    #2708: Fix ordering
    issues with custom-style elements that apply custom properties defined
    in other custom-style elements.

Release 1.2.2 (2015-11-12)

This release includes a number of small optimizations affecting startup time.

This release includes the following new features:

  • Fixes #2511. Add
    support for strip-whitespace attribute on templates. A template defined
    with the strip-whitespace attribute removes any empty text nodes from the
    template contents, which can result in a minor performance improvement.

  • Fixes #2537. Add optional
    incremental "chunked" rendering to dom-repeat.

    New properties:

    • initialCount. Enables incremental rendering and sets initial render count
    • targetFramerate. Determines the target frame budget for rendering the remaining items.

    If initialCount is set, after setting (or re-setting) items, the initial count will be rendered pre-paint, and all remaining items will be incrementally rendered at requestAnimationFrame timing. The template makes a best-effort attempt to hit
    the framerate specified by targetFramerate.

  • Fixes #2690. Add new
    getComputedStyleValue method to determine the computedn style of a custom
    property. Usage:

    propertyValue = element.getComputedStyleValue(propertyName);

    This is equivalent to the native:

    propertyValue = getComputedStyle(element).getPropertyValue(property);

This release includes the following bug fixes and improvements:

  • Fix compound bindings with braces in literals.

  • Fixes #2639. Fix for
    BEM-like CSS selectors under media queries. This issue affected CSS selectors
    that included two dashes inline, such as foo--bar.

  • Fixes #2641. Fix gestures
    when using shadow DOM polyfill.

  • Fixes #2649.
    queryAllEffectiveChildren method throws an exception.

  • Fixes #2650. Add support
    for short unicode escape sequences in CSS rules.

  • Fixes #2660. Fix parsing
    of custom properties with 'var' in value.

  • Fixes #2670. Fix
    for multiple consequent spaces present in CSS selectors.

  • Fixes #2685: dom-if
    throws exception if detached before instance is stamped.

Release 1.2.1 (2015-10-29)

This release includes the following new features:

  • Add deepContains method to DOM API.

This release includes fixes for the following issues:

  • Make parsing of mixin declarations more robust.

  • Fixes #2556.
    notifyPath: Ensure outer paths aren't forwarded to instance props.

  • Fixes #2610.
    isLightDescendant should return false for self.

Release 1.2.0 (2015-10-22)

This release includes the following new features:

  • Compound binding support. In place of a single binding annotation, you
    can now use a compound binding consisting of string literals and
    binding annotations:

    Name: {%raw%}{{lastname}}, {{firstname}}{%endraw%}

    See Compound bindings for details.

  • New observeNodes method for tracking addition and removal of child
    nodes and distributed nodes. See Observe added and removed children.

  • New effective children APIs that provide a composition-aware view of
    light DOM children. See Effective children.

  • Improvements to path API.
    Fixes #2007,
    #2509.

    • Allows set to take paths with array keys, identified by
      #key.
    • Allows notifyPath to take paths with array indices.
    • Exposes public notifySplices API.

  • Fixes #2582. Fix IE10 regressions
    in dom-repeat, dom-bind, and dom-module-inline

  • Fix deepEqual on Safari 9 due to Safari enumeration bug.

  • Add Polymer.dom(node).notifyObservers method to 'kick' observers, for example,
    when attributes change under Shadow DOM.

Release 1.1.5 (2015-10-08)

This release includes the following new features:

  • Added isLightDescendent and isLocalDescendent utility methods to
    {{site.project_title}} elements.

  • The fire method's detail argument can take any primitive value, not just objects.

This release fixes the following issues:

  • Fixes #2504. Templatizer: Variables in the parent scope are not passed during initialization.

  • Fixes #2505. Templatizer: Changes to array/object properties from the parent scope not notified.

Release 1.1.4 (2015-09-25)

This release fixes the following issues:

  • Fixes #2452. Work around
    a Chromium bug
    that caused memory to leak on page refresh.

  • Fixes #2048. Allow multiple
    paths to be linked using linkPath.

Web Components polyfill updated to 0.7.13. The latest version of webcomponents-lite.js
fixes an issue that affected SEO of Polymer 1.x apps.
{: .alert .alert-info }

Release 1.1.3 (2015-09-04)

  • Fixes #2403. Fixes a regression
    that affected legacy projects using Chrome 39.

Release 1.1.2 (2015-08-28)

  • Fixes #2356. Log a warning
    if the included style module cannot be found.

  • Fixes #2357. Styles included
    with include= are inserted before any styles defined in the body of
    the style element.

  • Fixes #2363. Explicitly create
    Polymer object on window to satisfy strict mode.

  • Fixes #2329. Registration changes
    to support ES6 classes.

  • Fixes #2341. Branch Polymer.dom to
    use native dom methods under Shadow DOM for appendChild, insertBefore, removeChild,
    replaceChild, and cloneNode.

  • Fixes #2334. When composing nodes
    in shady DOM, check if a node is where we expect it to be before removing it from
    its distributed position. We do this because the node may have been moved by
    Polymer.dom in a way that triggered distribution of its previous location. The
    node is already where it needs to be so removing it from its parent when it's no
    longer distributed is destructive.

Release 1.1.1 (2015-08-20)

This release fixes a serious regression in Release 1.1 related to shady DOM distribution. Related issues:

  • Fixes #2276: DOM API fails to select an element in a dom-repeat in Polymer 1.1. (commit)

  • Fixes #2311, #2323: When elements are removed from their previous position when they are added elsewhere, make sure to remove them from composed, not logical parent. (commit)

  • Fixes #2253: Refine logical tree check and populate parents of insertion points with logical info only if necessary. Fixes #2283: when a node is removed, we need to potentially distribute not only its host but also its parent. (commit)

Other fixed issues:

  • Fixes #2263: Ensure custom-style can parse variable definitions in supported selectors (e.g. /deep/) without exception due to unknown css. (commit)

  • array-selector: Add selectedItem property. (commit)

  • dom-repeat: Fixes #2297, Where a
    dom-repeat with a sort property threw an exception when removing 10 or more items at a time. (commit)

  • Fixes #2267: Properly find dom-module for mixed case elements. (commit)

  • Fixes #2304: Avoid trying to read style data from imports that did not load. (commit)

  • Support for negative numbers in computed bindings. (commit)

Release 1.1.0 (2015-08-13)

Shared style change

This release includes support for a new style sharing mechanism. The new mechanism
should be used in place of .

See Shared styles and external stylesheets in
the Developer guide for details.

As a result of these changes, several recommendations are changing:

  • is deprecated and will eventually be removed. This syntax
    allowed users to use a pure .css file, but the file is parsed as HTML which is a
    security and performance concern.

  • We now recommend placing an element's