New Extension API - Proposal

[Niro Samarakkody]

Howdy team,

Before I file a FR for this new extension API, I'd like to get your thoughts for this proposal. I am cc'ing Pega (partners requesting this api).

Mv3+

Public API

Namespace: chrome.user

API: chrome.user.data.dir to get the chrome user data directory path

API: chrome.user.profile.path to get the chrome user profile path

This allows extensions to send messages correctly to specific Chrome instances using the native messaging host.

Please reply-all with your feedback.

Thanks,

Niro Samarakkody, he/him

Chrome Enterprise Browser Specialist

nsamar...@google.com +1-650-457-7296

[Gibeau, Jeff]

Niro,

 

Thanks for the quick follow-up. Looking at the suggested APIs it appears that would provide what is needed for us to tie our native messaging host to the profile that it was launched under.

 

Thanks,

 

Jeff Gibeau | Director, Software Engineering | Robotic Automation | Pegasystems Inc.

Office: 1.678.527.5423 |Email: jeff....@pega.com

 

From: Niro Samarakkody <nsamar...@google.com>
Sent: Wednesday, May 4, 2022 12:13 PM
To: extension-...@chromium.org
Cc: Gibeau, Jeff <Jeffrey...@pega.com>; Blackwell, Becky <Becky.B...@pega.com>; David Li <ds...@google.com>; Benjamin Ackerman <acke...@google.com>
Subject: ExtMsg: New Extension API - Proposal

 

CAUTION: This email was sent from an EXTERNAL source. Think before clicking links or opening attachments.

[Niro Samarakkody]

Hi Extension API review team ,

Can you please provide some feedback?

Thanks,

Niro Samarakkody, he/him

Chrome Enterprise Browser Specialist

nsamar...@google.com +1-650-457-7296

[David Li]

Hi Niro,

Please file the bug as documented in the process. It can be updated and iterated on as needed, but it's good to just get the bug started so it can land in the right places for the appropriate individuals to comment on.

Best,

David