> 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.17.md).

# Release 1.7.17

Released to the Chrome Web Store on January 23, 2023

### ✨ Enhancements

* Page Editor: preserve unsaved changed when closing the Page Editor ([#4992](https://github.com/pixiebrix/pixiebrix-extension/pull/4992))
* Page Editor: warn when editing a blueprint that’s open in a different Page Editor tab ([#4992](https://github.com/pixiebrix/pixiebrix-extension/pull/4992))
* Brick/Integration Configuration: make links in field descriptions clickable ([#4993](https://github.com/pixiebrix/pixiebrix-extension/pull/4993))

### 🐛 Bug Fixes

* Fix performance bug in Page Editor that could cause lagging while typing ([#5000](https://github.com/pixiebrix/pixiebrix-extension/pull/5000))
* Support selector tool in configuration for Form Fill and Form Reader bricks ([#4989](https://github.com/pixiebrix/pixiebrix-extension/pull/4989))
* Highlight/Replace Text Bricks: don’t modify text in the head of the document ([#4996](https://github.com/pixiebrix/pixiebrix-extension/pull/4997))
* Fix file upload field in Form Builder ([#5007](https://github.com/pixiebrix/pixiebrix-extension/pull/5007))
* Page Editor: availability count shows incorrect/negative number ([#4944](https://github.com/pixiebrix/pixiebrix-extension/issues/4944))
* Page Editor: traces/statuses sometimes don’t appear (#4779)

### 🧱 Brick Updates

* Set Input Value: make the selector optional when the brick targets a field ([#4910](https://github.com/pixiebrix/pixiebrix-extension/pull/4990))
* Run AA Bot: update the Await Result functionality to be compatible with CR 0.27 ([#5048](https://github.com/pixiebrix/pixiebrix-extension/pull/5048))


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

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

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.