v1.2.0-beta1

Live Demo →
API Documentation →

New Features

Rendering

• By default, the notification uses the content provided by using the renderer callback function.
• The renderer function provides root, notification arguments.
  Generate DOM content, append it to the root element and control the state
  of the host element by accessing notification. Before generating new content,
  users are able to check if there is already content in root for reusing it.

Theme propagation

• the theme attribute value set on <vaadin-notification> will be propagated to the internal <vaadin-notification-card>.

Changes Since v1.1.0:

• 0078583 Rewrite notification sampler demo to not use Polymer [skip ci]

• c41a146 Improve renderers docs [skip ci]

• 3404dcb Propagate theme attribute to internal card

• 6b95c68 Update manual rendering test, do not render if not opened

• ad3b0e4 Add render method

• 2965e75 Add test for render method

• 3bf1df1 Align renderer API docs with context-menu [skip ci]

• f6dfc08 Move the renderer docs section upper [skip ci]

• 159a967 Capitalize Polymer, change to textContent, add br

• b55a00f Add demo with polymer template

• 977260a Update demos to prefer renderers

• 8c5140f Throw error and clean template or renderer when are assigned together

• d7f74cd Update tests for cases when renderer and template are assigned together

• 8de36e3 Add renderer (#77)

  • Add renderer tests

  • Add renderer implementation

  • Add renderer demo

  • Update docs and owner arg of renderer function

  • Update the renderer args order and test for it

  • Update demo wording

  • Update docs and demo

  • Bump analysis.json

  • Fix coveralls for PRs

  • Update renderer args and bump analysis.json

  • Remove public template, clean up model, bump analysis.json

• a638975 Added visual tests for Material theme. (#86)