Fixes the missing context menu issue on Google Chrome and improves overall extension stability.
Adds helpful notifications and direct links to setup guides if the extension cannot connect to your local text editor. It also ensures the extension works securely on all pages out of the box without requiring broad website permissions or showing scary warnings during installation.

Fixed bugs and enhanced UX

1. Fixed a bug in Chrome where the browser requested an explicit permission approval from the user,
   and the context menu didn't appear. Fixed by adding <all_urls> host permissions to ensure out-of-the-box functionality, and fixing a race condition.
2. Added native host error notifications. When the external editor can't be opened, a toast will now display a descriptive error message. For example, if the native messaging host is not installed, the message will show a list to the installation instructions.

Keyboard shortcut fixes and enhancements

• Show keyboard shortcut warning on options page and remove automatic migration
  (preserve user's choice). Automatic migration was removed because there is no
  reliable API to determine whether the shortcut was set by the user.
• Display the current shortcut and a button to change it
• Set the default shortcut to Ctrl+Shift+9 / Command+Shift+9 (unlikely to be
  intercepted by the OS/Browser)

Fixed: the keyboard shortcut could do nothing until you clicked the
toolbar icon or used the right-click menu first. The old default
shortcut (Ctrl+E, or Cmd+E on macOS) was being intercepted by the
browser or the operating system before it reached the extension, so
the editor never opened.

The default shortcut is now a combination that is not intercepted:
- Windows / Linux: Alt+Shift+E
- macOS: Control+Command+E

If you are upgrading: Firefox keeps your existing shortcut, and it is
updated to the new default automatically only if you were still using
the old one. If the shortcut still does not open your editor, reassign
it under about:addons > gear icon > "Manage Extension Shortcuts", and
avoid Ctrl+E / Cmd+E (these are reserved by the browser and the system).

The options page now helps you configure your editor correctly:

• A note explains that GUI editors must not fork into the background, with examples for common editors (GVim, Neovim Qt, Sublime Text, VS Code, VSCodium, Kate, Geany).
• If you type or have saved a command for a known GUI editor without the required foreground flag, a warning appears inline with the recommended fix — for example, suggesting gvim -f if you entered gvim without -f.

Fixed a bug where edited text was not updated in the textarea after saving and closing the external editor. This issue was particularly noticeable on macOS.

The native messaging host sends updates when you save the file and when you close the editor. Previously, only the first update was
processed, causing the final edited text to not appear in the textarea.

This release ensures all updates from the editor are properly applied to the textarea.

Fixed: GitHub pull request comment and description fields now properly recognize text inserted from the external editor.

Previously, the "Comment" / "Update comment" button would remain disabled until the user manually typed into the field.

The extension now dispatches the appropriate input/change events after updating text fields, ensuring GitHub’s UI reacts immediately.

Improved compatibility with GitHub and GitHub Enterprise textareas.

✨ New Features
• Context Menu Integration
Added a context menu (open it with right click) option to launch the external editor directly.
This feature is enabled by default and can be toggled in the extension settings.

🎨 UI & UX Improvements
• Options Page Modernization
The settings page has been redesigned for improved usability and aesthetics:
• System theme support (dark/light)
• Unified typography and layout
• Improved phrasing and readability
• Smooth transitions
• Bee-themed visual accents

The icon has been redesigned for better visual integration in browser UIs (including context menus).

✨ New Features
• Context Menu Integration
Added a context menu (open it with right click) option to launch the external editor directly.
This feature is enabled by default and can be toggled in the extension settings.

🎨 UI & UX Improvements
• Options Page Modernization
The settings page has been redesigned for improved usability and aesthetics:
• System theme support (dark/light)
• Unified typography and layout
• Improved phrasing and readability
• Smooth transitions
• Bee-themed visual accents

The icon has been redesigned for better visual integration in browser UIs (including context menus).

New Feature: Support for ${line} and ${column} placeholders in the command line settings

The Command Line field in the extension settings now supports two new placeholders:
- ${line} for the 1-based line number
- ${column} for the 1-based column number (offset from the beginning of the line)

Example usage:
/usr/local/bin/gvim --nofork +"call cursor(${line}, ${column})"

Notes:
- Quotes (single or double) are expanded similarly to shells.
- Variable expansion (like $VAR) and backslash escaping are not supported.
- Quotes are required when passing arguments that contain spaces. Without quotes, a line like +call cursor(${line}, ${column}) would be split into three arguments: +call, cursor(${line}, and ${column}).

New Feature: Support for ${line} and ${column} placeholders in the command line settings

The Command Line field in the extension settings now supports two new placeholders:
- ${line} for the 1-based line number
- ${column} for the 1-based column number (offset from the beginning of the line)

Example usage:
/usr/local/bin/gvim --nofork +"call cursor(${line}, ${column})"

Notes:
- Quotes (single or double) are expanded similarly to shells.
- Variable expansion (like $VAR) and backslash escaping are not supported.
- Quotes are required when passing arguments that contain spaces. Without quotes, a line like +call cursor(${line}, ${column}) would be split into three arguments: +call, cursor(${line}, and ${column}).

See https://github.com/rosmanov/chrome-bee/issues/12

Fixed Shadow DOM Traversal:
- Fields hidden behind the Shadow DOM are now correctly detected and traversed by the extension's content script.This fix restores the ability to invoke the external editor for Markdown comment editors and search fields on sites like Reddit.

Known Limitations
- Advanced Rich Text Editors: Fields rendered via internal state management (e.g., React-based editors) remain unsupported. Programmatic updates to these fields are still not reflected reliably, as these editors treat external input differently from direct user typing.

Removed host_permissions permission request

Also, performed some internal cleanup.

- Upgraded manifest version to version 3.
- Fixed a bug where editor text might was sent to all tabs instead of the calling tab.

- Extension settings are now stored in the sync storage area
- Translated to Russian

Fixed a bug in extension preferences where extension field and "Remove" buttons were not available.

Added support for custom filename extensions. The new feature works only with recent versions of the host application: either BeeCtl (https://github.com/rosmanov/bee-host) version 1.2.0 or newer, or the host app currently included in the extension repository (https://github.com/rosmanov/chrome-bee).

Note, BeeCtl binaries will be uploaded to SourceForge soon.

Fix: editor was not opened if no extension settings were ever saved.

Added support for a native messaging host written in C ( https://github.com/rosmanov/bee-host )
Fixed text field was not updated when the user switched to another tab
Changed event page is now converted to persistent background page

- Added support for the arguments accepted by a C implementation of the host app: https://github.com/rosmanov/bee-host
- Fixed: multiple editor windows were opened in Redmine