Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ChromeVox compatibility #12

Open
aleventhal opened this issue May 7, 2019 · 2 comments
Open

ChromeVox compatibility #12

aleventhal opened this issue May 7, 2019 · 2 comments

Comments

@aleventhal
Copy link
Owner

Since we can't use the native messaging messaging api to communicate with ChromeVox, we should just open an ordinary port.

Ideally, ChromeVox would be able to bundle js2at functionality without requiring the additional extension. However, this would require js2at to be more mature and ready to be bundled with Chrome.

So for now, let's just open up the additional port.

@aleventhal
Copy link
Owner Author

aleventhal commented May 10, 2019

Send to Chromevox port, id is mndnfokpggljbaajbnioimlmbfngpief

This is listed in Chrome source in contents.cc here:
https://cs.chromium.org/chromium/src/extensions/common/constants.cc?sq=package:chromium&g=0&l=100

@aleventhal
Copy link
Owner Author

Landed code that connects to ChromeVox via a port.
ChromeVox can listen with the following code:

chrome.runtime.onConnectExternal((port) => {
    if (port.name !== 'js2at->cvox')
      return;  // Not handled.

Also, ChromeVox will need to white list js2at under externally_connectable in the manifest, like:

externally_connectable:  {
   "ids": [
      "jpgoldinadnmhfknenolkgbnockemnid"
  ]
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant