Release 1.4.8 - update/reactivate blueprints from the active bricks page, and more!

Release 1.4.8 is now available in the Chrome Web Store

Release 1.4.8 includes one of my favorite new feature — the ability to update/reactivate blueprints from the Active Bricks page.

Release notes are available at: Release Notes

The next release is targeted for next week (the week of November 29th)

:sparkles: Enhancements

  • Ability to update/reactivate blueprints from the active bricks page (#1929)
  • Add extension version number to the footer (#1946)
  • Add support for targetMode to support passing through event target for context menu (#1948)
  • Adds support for targetMode to support running in the context of the selector for the trigger (i.e., the root ) instead of the eventTarget (#1930)

:bug: Bug Fixes

  • Trigger watch mode accumulates redundant triggers when used in Page Editor (#1928)
  • Saving a blueprint extension as a personal extension in the Page Editor now uninstalls the blueprint version of that extension (#1925)
  • Fix input/keyboard entry lag in Page Editor for some fields (#1923)

:brick: New Bricks / Brick Enhancements

  • @pixiebrix/wait/sleep to sleep a pre-determined amount of time (#1950)
  • Add a maxWaitMillis input argument for @pixiebrix/wait/element (#1950)
  • @pixiebrix/component-reader supports passing a blank selector to read from the inherited root element (#1948)
1 Like