Fixed an issue with editors that use the latest Monaco (e.g., Coderpad), which prevented detection of the element to edit.

Fixed an issue that caused marked text to reset in Emacs when used in Overleaf and other CodeMirror 6 editors.

Fixed simulated clicks for iframe environments. Previously, when using editors like TinyMCE embedded in iframes, simulated clicks would fail to locate elements outside the iframe, resulting in an "element not found" error. This update adjusts the search context to properly locate and click the intended button elements even when the editor is isolated within an iframe.

Version 0.9.0

• Added support for executing clicks on the elements defined by the user (for example, to click "Send" in Slack after editing). The list of allowed sites and elements' CSS selectors is described in the atomic-chrome documentation.

- Added support for Slack and other Quill-based editors.
- Now, changes you make in content-editable elements include the full inner HTML markup. This means that when you edit text, any formatting you applied—such as bold, italic, or structured line breaks—is preserved exactly as displayed. Previously, only the plain text might have been captured, sometimes resulting in lost or altered formatting. With this update, you can expect a more consistent and faithful editing experience that mirrors what you see on screen.

- Added a context menu for editable elements.
- Added support for `TinyMCE` and other iframe-based editors.

- Added support for `CKEditor 4` and `CKEditor 5`. Introduced bidirectional editing functionality, though scroll synchronization remains unsupported.
- Improved keyboard input handling for editable elements. Previously, hint key presses (used to navigate editable areas) could be intercepted by active elements such as rich text editors, resulting in missed actions. To resolve this, a temporary `textarea` mask is now dynamically positioned to intercept and handle hint keys correctly without interfering with the underlying editor.

- Implemented a keep-alive mechanism for Firefox using the Alarms API.
- Removed redundant keep-alive logic from the content script, centralizing it in the background script.
- Updated the manifest to ensure appropriate permissions for the Alarms API in Firefox.

- Reduced the keep-alive interval to seconds to prevent disconnection during idle periods.