> For the complete documentation index, see [llms.txt](https://docs.pixiebrix.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.pixiebrix.com/release-notes/release-notes-archive/release-1.7.16.md).

# Release 1.7.16

Published to the Chrome Web Store on January 9, 2023

&#x20; 🧑‍💻 A complete listing of code changes [are available on GitHub](https://github.com/pixiebrix/pixiebrix-extension/milestone/65?closed=1)

### ✨ Enhancements

* Page Editor: add ability to re-configure the blueprint options without re-activating from the Blueprints Screen ([#2390](https://github.com/pixiebrix/pixiebrix-extension/issues/2390))
* Page Editor: warn on invalid regular expressions in the Regex Extractor brick ([#4904](https://github.com/pixiebrix/pixiebrix-extension/pull/4904))
* Page Editor: warn on invalid URLs when using HTTP Request brick ([#4941](https://github.com/pixiebrix/pixiebrix-extension/pull/4941))
* Page Editor/Runtime: add support for passing an element as the target for DOM bricks ([#4875](https://github.com/pixiebrix/pixiebrix-extension/pull/4875))
* Blueprints Screen: Add Publish to Marketplace Action ([#4765](https://github.com/pixiebrix/pixiebrix-extension/issues/4765))
* Show secret/key fields as password fields ([#4831](https://github.com/pixiebrix/pixiebrix-extension/pull/4831))
* Add support for integrations using HTTP Basic Auth ([#4917](https://github.com/pixiebrix/pixiebrix-extension/pull/4917))

### 🐛 Bug Fixes

* Workshop: fix bug where data would reset on server validation error ([#4811](https://www.notion.so/Release-Notes-d18eaa68c28d44c18e2a167c7d17f497?pvs=21))
* Sidebar: fix bug where repeat calls for Display Temporary Information brick would show a blank panel ([#4915](https://github.com/pixiebrix/pixiebrix-extension/pull/4915))
* PixieBrix was reporting 4XX and 5XX network errors as connectivity issues and/or blocked requests ([#4813](https://github.com/pixiebrix/pixiebrix-extension/pull/4813))
* For button and initialize trigger, consider page changes in all elements, not just mutated/newly added elements ([#4943](https://github.com/pixiebrix/pixiebrix-extension/pull/4943))

### 🧱 New Bricks

* Replace Text brick to transform/mask text ([#4864](https://github.com/pixiebrix/pixiebrix-extension/issues/4864))
* Highlight Text brick to highlight text with a color ([#4907](https://github.com/pixiebrix/pixiebrix-extension/pull/4907))
* Traverse Elements brick to find elements relative to another element ([#4875](https://github.com/pixiebrix/pixiebrix-extension/pull/4875))

### ⚛️ Experimental

&#x20;⚛️ Want access to experimental features? Contact <support@pixiebrix.com> or reach out in [the PixieBrix Slack community](https://slack.pixiebrix.comcom/)

* Page Editor: variable selection popover ([#4690](https://github.com/pixiebrix/pixiebrix-extension/issues/4690), [#4691](https://github.com/pixiebrix/pixiebrix-extension/issues/4691))


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.pixiebrix.com/release-notes/release-notes-archive/release-1.7.16.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
