CrossPilot

Getting Started

CrossPilot allows you to install addons from Opera webstore and CRX files. Most common used APIs are supported by CrossPilot so most of the addons are already compatible with CrossPilot but if your addon is not working with CrossPilot, you can use the documentation to make it compatible.

• Install Opera webstore
• Install CRX file
• Automatic updates

How to install an addon from Opera webstore?

Installation from Opera addons webstore is really easy simple.

• Install CrossPilot from Chrome webstore.
• Visit Opera addons webstore and find your desired addon.
• Click on Install with CrossPilot button in sidebar.
• Installation process will begin in CrossPilot installation page.
• You are ready to use your Opera addon in Chrome.
• Note If the addon is not compatible, you will see an error message.

How to install an addon from a CRX file?

• Install CrossPilot from Chrome webstore.
• Open CrossPilot options page.
• Click on Choose File button and select CRX file.
• Installation process will begin in CrossPilot installation page.
• You are ready to use your addon in Chrome.
• Note If the addon is not compatible, you will see an error message.
• Note Updates are not supported for CRX files.

Automatic Updates

Auto updates are only supported for Opera webstore addons and hosted addons.

Manifest

• Supported items
• Content scripts
• Web accessible resources

Supported items

CrossPilot supports following manifest items:

• default_locale
• icons
• browser_action
• options_ui
• background
• content_scripts
• web_accessible_resources

Content scripts

• Content scripts are executed on document_end without sandbox.
• Chrome locale API is supported.
• Note chrome.runtime.getURL is supported and returns files as base64 encoded data urls.

Web accessible resources

Web accessible resources are partially supported. They are only available through chrome.runtime.getURL and are returned as base64 encoded data urls.

Optional Permissions

CrossPilot supports following permissions and we are working to add support for more. These permissions are only requested when user installs an extension.

• http://*/*
• https://*/*
• alarms
• storage
• tabs
• downloads

Supported Chrome APIs

• chrome.alarms
• chrome.browserAction
• chrome.downloads
• chrome.extension
• chrome.i18n
• chrome.permissions
• chrome.runtime
• chrome.storage
• chrome.tabs
• chrome.windows

XMLHttpRequest

Chrome's sandbox environment does not allow you to make XMLHttpRequests. We have added a custom polyfill that will translate your requests through our API and you will not see any difference or need to make any change to make your addon compatible.

Note fetch API is not supported, please add your own polyfill if you are using fetch API.

Local Storage

Chrome's sandbox environment does not allow access to local storage API. We have added a polyfill that uses Chrome extension storage API to sync local storage for your addon. Your addon will still be able to function with sync functions.