> For the complete documentation index, see [llms.txt](https://gaffa.dev/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gaffa.dev/docs/changelog/2026/may.md).

# May

### API Updates

#### **`Scroll` action now supports a selector parameter** 

[`scroll`](/docs/features/browser-requests/actions/scroll.md) action now accepts an optional `selector` parameter, allowing you to scroll a specific element on the page rather than the page body.

#### **`block_ads` parameter added** 

A new [`block_ads`](https://gaffa.dev/docs/features/browser-requests/settings#a-d-blocking) parameter is now available in request settings. When set to `true`, Gaffa intercepts and aborts requests to known ad domains before they load, reducing page load times on ad-heavy sites. 

#### **`generate_markdown` output improved**

We've made behind-the-scenes improvements to the [`generate_markdown`](https://gaffa.dev/docs/features/browser-requests/actions/generate-markdown) action, refining the output response format and expanding support for a greater variety of HTML elements. The result is cleaner, more consistent markdown across a broader range of pages.

### Samples, Blog & Tutorials

#### Speed up your scraping with ad blocking

We published a breakdown of how enabling [`block_ads`](https://gaffa.dev/docs/features/browser-requests/settings#a-d-blocking) cuts unnecessary ad network requests before they load, reducing page load times by up to 50% on ad-heavy sites. We tested it across The Guardian, Allrecipes, and Daily Mail, and also showed how combining it with [`max_media_bandwidth`](https://gaffa.dev/docs/features/browser-requests/settings#max-media-bandwidth) pushes performance even further. [Read the blog.](https://gaffa.dev/blog/speed-up-your-scraping-with-ad-blocking)


---

# 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://gaffa.dev/docs/changelog/2026/may.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.