# 24 January: Widget in iFrame

### ✨ New

In this update, we've transitioned from utilizing a widget as a web component to incorporating iframes, introducing a range of enhancements.

**Benefits of the Changes:**

1. **Enhanced Style and Script Isolation:**
   * With the adoption of iframes, we've achieved complete isolation of CSS styles and JavaScript scripts. This ensures a conflict-free environment, eliminating issues related to class names, functions, or variables between your application and the iframe content.
2. **Heightened Security Measures:**
   * Your application's security is now fortified as iframes restrict access to embedded webpage content. This prevents embedded content from having direct access to global resources and functions within your application.
3. **Simplified Integration with External Applications:**
   * The switch to iframes streamlines the integration process with external services or applications. More straightforward and reliable integration, providing a seamless experience for external content.


---

# 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://changelog.transactionlink.io/january-2024/24-january-widget-in-iframe.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.