Date: Fri, 24 Jul 2015 04:52:51 +0000 From: bugzilla-noreply@freebsd.org To: chromium@FreeBSD.org Subject: maintainer-feedback requested: [Bug 201805] [PATCH] www/chromium: enable native message service API for extensions Message-ID: <bug-201805-28929-VMaRArHTKQ@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-201805-28929@https.bugs.freebsd.org/bugzilla/> References: <bug-201805-28929@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
Matthias Petermann <matthias@petermann-it.de> has reassigned Bugzilla Automation <bugzilla@FreeBSD.org>'s request for maintainer-feedback to chromium@FreeBSD.org: Bug 201805: [PATCH] www/chromium: enable native message service API for extensions https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=201805 --- Description --- Created attachment 159130 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=159130&action=edit Patch for enabling native messaging Chrome / Chromium are supporting a native Messaging API[1] which is useful to interact with external processes from as Chrome app. There is a good usage example available, too[2]. The current Chromium on FreeBSD doesn't support native Messaging due this is implicitly excluded in the respective source code file at compile time. This results in Chromium returning an error message when trying to open a channel to an external process: "native Messaging is not supported on this platform." Adding OS_FREEBSD to the expression makes this work and can be successfully tested. Please find the patch attached to this report. [1] https://developer.chrome.com/extensions/nativeMessaging [2] https://chromium.googlesource.com/chromium/src/+/master/chrome/common/extension s/docs/examples/api/nativeMessaging
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-201805-28929-VMaRArHTKQ>