# Browser Event Block

<figure><img src="/files/9PQAuFpGmTqEVAipeJGN" alt=""><figcaption></figcaption></figure>

Await the triggering of the selected event before running the next block.

* **Timeout (milliseconds)**\
  Set the workflow timeout for the selected event (by default, it is 10000ms - 10 seconds). After the time is up, the workflow continues to execute the block.
* **Events.** An event you would like the workflow to await.
  * **Tab closed.** Wait until a tab has closed.
  * **Tab loaded.** Wait for the current tab or the tab that the URL matches the [match patterns](https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/Match_patterns#examples) to be loaded.
  * **Tab/Window created.** Wait for a new tab/window to be created. A filter is provided for this setting.
    * **Filter.** Filter the URL for the new tab or window. If the URL matches the URL or Regex you entered, the workflow will keep running the blocks.
    * **Active tab.** Define the created tab or window as the current tab.
  * **Window closed.** The event occurs when the window closes.


---

# Agent Instructions: 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:

```
GET https://docs.goless.com/blocks/browser/browser-event-block.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
