v1.7.0-alpha2

Live Demo →
API Documentation →

Changes Since v1.7.0-alpha1:

• 43a4ba6 feat: add TS definitions for css literals (#100)

v1.7.0-alpha1

Live Demo →
API Documentation →

Changes Since v1.6.1:

• 9d11e59 feat: expose style modules as css literals (#94)

v1.6.1

Live Demo →
API Documentation →

Changes Since v1.6.0:

• 4313e78 fix: add icons sketch file to bower ignore list (#95)

• 1458482 chore: fix modulizer to use correct Lumo (#96)

• 4d5a6db refactor: font builds should probably ignore run timestamp for consistency [1]

  1: #88 (comment)

• c242ec7 fix: icons build glyph sort should be normalized for platform-independence

  gulp-iconfont bump pulls in required version range of
  gulp-svgicons2svgfont with relevant file sort module changes.

  Avoids font-icons.html unintentional codepoint changes like:

  diff --git a/font-icons.html b/font-icons.html
  index e4f9b52..63476b3 100644
  --- a/font-icons.html
  +++ b/font-icons.html
  @@ -38,8 +38,8 @@
         --lumo-icons-dropdown: "\ea18";
         --lumo-icons-edit: "\ea19";
         --lumo-icons-error: "\ea1a";
  -      --lumo-icons-eye: "\ea1b";
  -      --lumo-icons-eye-disabled: "\ea1c";
  +      --lumo-icons-eye-disabled: "\ea1b";
  +      --lumo-icons-eye: "\ea1c";
         --lumo-icons-menu: "\ea1d";
         --lumo-icons-minus: "\ea1e";
         --lumo-icons-ordered-list: "\ea1f";

  Refactor base64 shell utility to Node-native, avoid cross-platform
  incompatibilities like [1]

  1: https://stackoverflow.com/questions/46463027/base64-doesnt-have-w-option-in-mac

• e4397fc fix: Node 12+ crashes gulp icons, requires gulp-^4.0.0

  Fix #85

  • gulp-^4.0.0 is provided by @vaadin/vaadin-component-dev-dependencies-^2.0.0

  • .eslintrc.json: async functions require parserOptions.ecmaVersion = 8

  • Gulpfile: Gulp 4 task architecture uses gulp.series() and
    .parallel() async strategy

    We use .parallel() only for lint tasks operating on distinct file sets

  • Gulpfile: add simple .on('error') report callbacks to task pipelines
    missing such, avoid events.js unhandled 'error' event warnings if
    any pipeline reports errors

  • Gulpfile: on Linux, base64 requires explicit -w 0 to disable line wrapping

  TODO Not sure why font-icons.html output produces a reverse of
  unicode characters for --lumo-icons-eye vs --lumo-icons-eye-disabled.
  Is the original commit faulty perhaps?

  TODO Test for #66

v1.6.0

Live Demo →
API Documentation →

Changes Since v1.5.0:

• 702b981 Add rtl specific styles (#78)

• 5334eb2 update to xenial

• b8fd7ab docs(customization): update vaadin-themable-mixin docs links

  vaadin-themable-mixin documentation has been moved from the GitHub Wiki
  to the README.

v1.5.0

Live Demo →
API Documentation →

New Features

• Option to import the SVG icon set (<iron-iconset-svg>) without automatically importing <iron-icon> by importing iconset.html instead of vaadin-icons.html (#65, #67)

Changes Since v1.4.3:

• 842117e feat: provide iconset import without iron-icon dependency (#67)

  Split iconset definition from icons.html into new iconset.html (which is then imported in icons.html).
  This makes it so importing icons.html works as before (and includes import of iron-icon) to maintain backwards compatibility, but now the developer also has the option to import the iconset without the iron-icon dependency by importing iconset.html directly. This is useful in some cases like when doing lazy asynchronous imports.

  Fixes #65

v1.4.3

Live Demo →
API Documentation →

Changes Since v1.4.2:

• 2e42fd1 fix: include presets/compact.js in npm release

  Fixes #71.

v1.4.2

Live Demo →
API Documentation →

Fixes

• Fixed the regression affecting badge "pill" variant border-radius

Changes Since v1.4.1:

• 12bbea0 fix: use border-radius-s for pill badge variant (#64)

• 164f05b Add missing field to bower.json for 1.4.1 npm version

v1.4.1

Live Demo →
API Documentation →

Fixes

Fixed --lumo-border-radius deprecation, so that existing theme customizations still work as expected.

Until all components using Lumo have been updated to use the new roundness properties, you should keep using the deprecated --lumo-border-radius property for controlling the medium roundness. Otherwise you might get mixed results, some components being affected and others not.

After you’ve updated your component dependencies to versions that use the new roundness properties, you can switch from --lumo-border-radius to --lumo-border-radius-m in your theme overrides.

Changes Since v1.4.0:

• e348eb0 Revert breaking change to --lumo-border-radius (#61)

• dab9a79 chore(package): add all-imports.html to use as a main field (#60)

v1.4.0

Live Demo →
API Documentation →

Changes Since v1.3.3:

• b0fa4b7 Add more border radius and box shadow variants (#57)

  • Add 3 degrees for border radius properties
  • Deprecate the “global” --lumo-border-radius property
  • Add a small shadow variant

• 2c1e003 Add --lumo-clickable-cursor and use it in field button mixin (#56)

• 20d5b90 Fix linter issues

• 402850f Update package.json

• 61b22e7 Update travis config

• 559afa5 Add compact preset

• 29c99ae Explicitly specify port in 'npm start' script

• 093dcfd Add missing dom-module imports for typography and color

• 49a58a1 Add 'npm start' script

• d09e0b6 Force block formatting for field-button icon element

  Fixes vaadin/vaadin-date-picker#602

• 091a837 Add missing colors to documentation

  The 10% tint, shade, and contrast colors were missing from the light palette properties docs.

v1.3.3

Live Demo →

Changes Since v1.3.1:

• 01e3721 vaadin-dropdown-menu -> vaadin-select

• c4a96fb Bump devDeps to stable versions