Skip to content

Releases: vaadin/vaadin-context-menu

v4.3.0-alpha2

28 Jan 11:58
Compare
Choose a tag to compare

Live Demo →
API Documentation →

Changes Since v4.3.0-alpha1:

  • 8bc86ef Explicitly specify port in 'npm start' script

  • 5a29bcb Enable menu close on backdrop click (#202)

v4.3.0-alpha1

21 Dec 08:19
Compare
Choose a tag to compare

Live Demo →
API Documentation →

Changes Since v4.2.1:

v4.2.1

07 Dec 13:06
Compare
Choose a tag to compare

Live Demo →
API Documentation →

Fixes

  • Removed list-box and item imports from Material theme to prevent possible 404

Changes Since v4.2.0:

  • 6d01c93 Align with skeleton: use latest vaadin-demo-helpers, improve demos

  • c39274f Remove list-box and item imports from Material theme (#198)

  • dab9112 Add note that vaadin-list-box should be imported separately

  • 65ebae1 Update dependencies to stable versions

  • bc6c046 Fix context menu basic example to mention renderer

v4.2.0

23 Oct 07:15
Compare
Choose a tag to compare

Live Demo →
API Documentation →

New Features

Rendering

  • By default, the context menu uses the content provided using the renderer callback function.
  • The renderer function provides root, contextMenu, model arguments when applicable.
    Generate DOM content by using model object properties if needed, append it to the root
    element and control the state of the host element by accessing contextMenu. 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-context-menu> will be propagated to the internal <vaadin-context-menu-overlay> component

Changes Since v4.1.0:

  • 41e88a5 Move core overlay background style from content part to overlay part. Fixes #181

  • 486870a Propagate theme attribute to internal overlay

  • cb73b7e Update overlay dependnecy, fix test for manual rendering

  • bd5dc49 Add render method and temporary update overlay dependency

  • 693b651 Add test for render method

  • 91c2bbd Update grid and overlay dependencies

  • 7199e2f Reuse dom in the docs example [skip ci] (#183)

  • 91b9108 Remove guardian statement and change the order of args [skip ci]

  • 85111dc Move the renderer docs section upper [skip ci]

  • 28b0b68 Replace new with createElement in demos to avoid errors in P3 [skip ci] (#180)

  • 5e154b7 minor changes to demo [skip ci]

  • 82d49b4 Update demos to prefer renderers [skip ci] (#176)

  • c53c369 Remove new template or renderer on error

  • 2918459 Add polymer util import, simplify property assignment and flush test

  • 93e8e80 Update tests

  • 2820da9 Add observer for throwing error, usage of renderer and template

  • 7db937b Add test for throwing error for template and renderer

  • 0316819 Add multiple calls note to renderer JSdoc description

  • 7a0a668 Add renderer support

v4.2.0-beta2

09 Oct 09:47
Compare
Choose a tag to compare

Live Demo →
API Documentation →

Fixes

  • Fixed the npm published version

Changes Since v4.2.0-beta1:

  • 573e1a5 Remove Polymer mention from package description

v4.2.0-beta1

04 Oct 08:56
Compare
Choose a tag to compare

Live Demo →
API Documentation →

New Features

Rendering

  • By default, the context menu uses the content provided using the renderer callback function.
  • The renderer function provides root, contextMenu, model arguments when applicable.
    Generate DOM content by using model object properties if needed, append it to the root
    element and control the state of the host element by accessing contextMenu. 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-context-menu> will be propagated to the internal <vaadin-context-menu-overlay> component

Changes Since v4.1.0:

  • 41e88a5 Move core overlay background style from content part to overlay part. Fixes #181

  • 486870a Propagate theme attribute to internal overlay

  • cb73b7e Update overlay dependnecy, fix test for manual rendering

  • bd5dc49 Add render method and temporary update overlay dependency

  • 693b651 Add test for render method

  • 91c2bbd Update grid and overlay dependencies

  • 7199e2f Reuse dom in the docs example [skip ci] (#183)

  • 91b9108 Remove guardian statement and change the order of args [skip ci]

  • 85111dc Move the renderer docs section upper [skip ci]

  • 28b0b68 Replace new with createElement in demos to avoid errors in P3 [skip ci] (#180)

  • 5e154b7 minor changes to demo [skip ci]

  • 82d49b4 Update demos to prefer renderers [skip ci] (#176)

  • c53c369 Remove new template or renderer on error

  • 2918459 Add polymer util import, simplify property assignment and flush test

  • 93e8e80 Update tests

  • 2820da9 Add observer for throwing error, usage of renderer and template

  • 7db937b Add test for throwing error for template and renderer

  • 0316819 Add multiple calls note to renderer JSdoc description

  • 7a0a668 Add renderer support

v4.2.0-alpha2

06 Sep 11:33
Compare
Choose a tag to compare

Live Demo →
API Documentation →

Changes Since v4.2.0-alpha1:

  • 41e88a5 Move core overlay background style from content part to overlay part. Fixes #181

  • 486870a Propagate theme attribute to internal overlay

  • cb73b7e Update overlay dependnecy, fix test for manual rendering

  • bd5dc49 Add render method and temporary update overlay dependency

  • 693b651 Add test for render method

v4.2.0-alpha1 - Renderer

27 Aug 07:19
Compare
Choose a tag to compare

Live Demo →
API Documentation →

New Features

Rendering

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

Changes Since v4.1.0:

  • 91c2bbd Update grid and overlay dependencies

  • 7199e2f Reuse dom in the docs example [skip ci] (#183)

  • 91b9108 Remove guardian statement and change the order of args [skip ci]

  • 85111dc Move the renderer docs section upper [skip ci]

  • 28b0b68 Replace new with createElement in demos to avoid errors in P3 [skip ci] (#180)

  • 5e154b7 minor changes to demo [skip ci]

  • 82d49b4 Update demos to prefer renderers [skip ci] (#176)

  • c53c369 Remove new template or renderer on error

  • 2918459 Add polymer util import, simplify property assignment and flush test

  • 93e8e80 Update tests

  • 2820da9 Add observer for throwing error, usage of renderer and template

  • 7db937b Add test for throwing error for template and renderer

  • 0316819 Add multiple calls note to renderer JSdoc description

  • 7a0a668 Add renderer support

v4.1.0

21 Aug 08:51
Compare
Choose a tag to compare

Live Demo →
API Documentation →

Changes Since v4.1.0-beta2:

  • 5b0d534 Update dependencies to stable versions

  • b568e78 Update vaadin-element-mixin to 2.0.0

  • d24a7f9 Run tests in headless Chrome and Firefox, use sudo: false in travis

  • e897a00 Remove analysis.json [skip ci]

  • 5c9b64a Exclude visual tests for PR builds in travis [skip ci]

  • ab27488 Use badgen for npm and bower versions badges [skip ci]

  • 5d66500 Use @vaadin/vaadin-component-dev-dependencies

v4.1.0-beta2

27 Jul 17:41
Compare
Choose a tag to compare

Live Demo →
API Documentation →

Changes Since 4.1.0-alpha3:

  • cad03cb Update bower main to inclue MD for modulizer conversion
  • 885e0d0 Update vaadin dependencies
  • 0c2b12f Fix tests for IE11 and Polymer 3 with new modulizer (#173)
  • d6314ab Use stable polymer-modulizer
  • 9710dce Re-organize demo structure (#166)
  • 2b585e5 Fix Bower semver ranges (#168)
  • 8c8fb00 Fixed end of line problem with gulp-html-extract plugin on Windows.