0.11.2: Hotfix

• Fixed fontKerning resetting to 'auto' after canvas resize

0.11.1: Change default fontKerning

• Force 'normal' fontKerning instead of 'auto' in default context state
  • This prevents issues where different environments lead to different rendering results and text measurements

0.11.0: Change default font size

• Avoid using rem for default font sizes for consistent sizes
  • Previously it was 1rem, but now it's 16px. This should be more consistent across different devices, while looking the same as before on most devices
  • Note, however, that this is a breaking change in some cases, especially if you're using lazy-widgets-wle

0.10.16: Revert 0.10.15

This release reverts the changes from 0.10.15 as they were breaking changes. The changes will be moved to 0.11.0

0.10.15: Change default font size

• Avoid using rem for default font sizes for consistent sizes
  • Previously it was 1rem, but now it's 16px. This should be more consistent across different devices, while looking the same as before on most devices

0.10.14: More ScrollableViewportWidget features

Changes

• Added scrollbarCornersRadii and scrollbarPadding to BaseTheme

0.10.13: Expose ScrollableViewportWidget fields/methods

Changes

• Turned most of ScrollableViewportWidget's fields and methods from private to protected to allow custom scrollbar rendering

0.10.12: ThemeScope improvements

Changes

• Allow ThemeScope.scopeTheme to be set

Fixes

• Add missing properties argument to ThemeScope constructor

0.10.11: Types and tooling fixes

Fixes

• Fixed types of registerFactory, registerFactoryFromClass and autoRegisterFactory from BaseXMLUIParser by adding a new WidgetConstructor type
• Fixed failed documentation generation
  • Updated TypeDoc to version 0.26.11
• Fixed failing tests
  • Updated jsdom to 25.0.1
  • Replace canvas package with @napi-rs/canvas to prevent an issue with newer versions of node (it's also faster!)

0.10.10: Hotfix

Fixes

• Fixed 0-sized SVGs on Firefox
  • If an HTMLImageElement has a natural width/height of 0 and is loaded, then 150 will be used as a fallback value. This may lead to images with incorrect aspect ratios, but unfortunately there's nothing that can be done, because Firefox and Safari are the new Internet Explorer