v1.3.3

Bug Fixes

• #1610 - engine: This change fixes a bug where setting the spellcheck attribute to "false" in the template resulted in a value of "true" being rendered in the DOM. It's worth noting that this change does not address the same issue when setting spellcheck to "false" via template expressions, which will be subsequently revisited if the need arises.

v1.3.2

Internal

• #1738 - errors: Eliminates the dependency that @lwc/jest-transform has on @lwc/errors. This is a required step to make @lwc/errors truly private.

v1.3.1

Bug Fixes

• #1724: Update release script to reflect the correct package version in the distribution file. LWC distribution files are generated along with a version number comment. This change fixes a bug where the release script was incorrectly using the version number of the previous release.

v1.3.0

Improvements

• #1722 - synthetic-shadow: Default implementation for programmatic focus when delegating focus. Components using delegatesFocus now have a focus() method that follows shadow semantics and focuses on the first focusable element in its shadow tree. This change is backwards compatible with components that define their own focus() method.

v1.2.5

Bug Fixes

• #1723 - synthetic-shadow: Pass arguments through to the underlying native focus() method. Our patch for HTMLElement.prototype.focus() was ignoring any optional arguments that may have been passed to the method.

v1.2.4

Bug Fixes

• #1709 - synthetic-shadow: Refine the focus delegation behavior. The focus delegation polyfill assumed that any element with an href attribute was sequentially focusable via keyboard. This was tightened to only consider a and area tags with href attributes. In addition, iframes have also been added to the list of sequentially focusable elements.

v1.2.3

Improvements

• #1711 - engine: Add support for the isConnected property on component instances. This property
  can be used to check if the instance is connected to the DOM.

Bug Fixes

• #1681 - wire-service: Fix a bug to discontinue usage of WireContextEvent event type to be consistent with the event naming standard. wirecontextevent should be used instead.

Internal

• #1703, #1710, #1713 Upgrade Node(12.15.0) and Yarn(1.22.0) versions used by the project. Upgrade handlebars dependency from 4.0.12 to 4.7.3. Upgrade dev dependencies
• #1717 - engine: Remove unused currentContext functionality which was storing context before invoking component callbacks.

v1.2.2

Bug Fixes

• #1704 - engine: Fix an infinite loop that was introduced during an internal refactor of how we resolve error boundaries. This bug was introduced in v1.2.0.

Internal

• #1696 - synthetic-shadow: Enable the toggling of feature flags used in the @lwc/synthetic-shadow polyfill. This change stores feature flag values globally such that all packages share a single instance of feature flags.

v1.2.0

Improvements

• #1687 - template-compiler: Add support for content attributes with leading hyphens. Until now, component authors were able to define component properties in Pascal case but users were not able to set those properties in their templates. Users can now set the value of a Pascal case property by adding a leading hyphen to the attribute (e.g., @api FooBar can be set via -foo-bar={awesomeValue})
• #1679 - wire-service: Add support for the lowercase event type wirecontextevent in addition to the currently supported event type WireContextEvent. This allows component authors to avoid engine warnings triggered when using event types with capital letters. WireContextEvent is now deprecated and will be removed in a future release.

Bug Fixes

• #1676 - synthetic-shadow: Fix a bug in the Event polyfill so that the composed option is respected when instantiating an instance of Event. The previous behavior ignored the composed option and only considered the type of the event when accessing the composed property of an Event instance. This polyfill exists to normalize the behavior of some browsers that incorrectly set the composed property of natively composed events.

Internal

• #1682: Remove usage of white/black as good/bad. Implements the “tone” guidelines for the WHATWG style guide.
• #1648 - engine: Remove the instanceof Event check in LightningElement.prototype.dispatchEvent. The same check is run by the browser when invoking the EventTarget.prototype.dispatchEvent method. Reduces the coupling between the engine and the DOM in preparation for server side rendering.
• #1668, #1674, #1675: Review all disabled karma integration tests. Enable tests that can be enabled. Remove tests that are no longer relevant. Refactor tests appropriately based on their relevancy (native vs synthetic shadow).
• #1669 - karma-integration: Port existing webdriver integration tests to karma. Delete unnecessary tests. The goal here is to reduce the number of integration tests to the strict minimum to increase the integration test passing rate.
• #1692 - engine: Refactor the way error boundaries are computed by decoupling the logic from the DOM.
• #1683 - features: Fix a bug where unary negation of a runtime feature flag was being interpreted as a compile-time boolean false.
• engine: Improve our usage of internal types.
• #1694 - features: Remove support for feature flags as computed properties. This means that featureFlags['ENABLE_FOO'] will no longer work and should be referenced as featureFlags.ENABLE_FOO instead.
• #1652 - synthetic-shadow: Add tsc as part of the build. tsc should run before rollup to catch TypeScript-related errors.

v0.40.1-222.8

v0.40.1-222.8