Can you add some details on why this needs to be done?  We don't like to whitelist apps if we can help it.

We need a way to toggle spoken feedback on a touch-only device. Originally we were going to do this natively but we decided to instead signal CFM when we detect a two-finger hold gesture and then let them add their own UI / feedback and toggle spoken feedback directly.

I added a new private API for them in accessibilityPrivate.

They're already whitelisted for several other private APIs so I was hoping this would make sense.

rdevlin, do you need additional information, or can we get this in?

After consulting with +lazyboy@, this seems reasonable to me. I don't have any objections. 

@rdevlin, please shout if you have any concerns once you're back in the office.

Do we need *all* these different IDs?  Feature whitelists are cheap-ish, but not free.  Additionally, is there any way we can further limit the scope of this?  If the app only needs one API method, can we whitelist them for just that method?  If it should only be used from e.g. kiosk mode, we can whitelist them for just those sessions.

I know very little about how this whitelisting works, but what is needed is

- the two listeners chrome.accessibilityPrivate.onTwoFingerTouchStart and chrome.accessibilityPrivate.onTwoFingerTouchStop
- in kiosk mode

We need all the app ids because of the release process we have in place, so sadly we can't prune that list.

In other words, both limiting the methods and the mode like you suggested seems like a perfectly reasonable solution.

Can you or lazyboy@ throw together such a CL, or give directions to Felix how to do it? It would be much appreciated.

Cool!  So we should be able to limit the scope significantly.  Unfortunately since we need two events, this will mean *more* features, but the increased security from not exposing more features is probably worthwhile.

Changing the whitelisting should be pretty straightforward, but I'm still essentially OOO this week.  lazyboy@, mind taking the review?  (I've added you to it.)

@Comment 9, will do.

Untriaged w/ owner -> assigned

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/ecf6be1dcf5f2fd0dd190742381d9dd52c0f3d26

commit ecf6be1dcf5f2fd0dd190742381d9dd52c0f3d26
Author: felixe <felixe@chromium.org>
Date: Mon May 22 21:18:40 2017

Whitelist accessibilityPrivate APIs

BUG= 717501 

Review-Url: https://codereview.chromium.org/2857143002
Cr-Commit-Position: refs/heads/master@{#473700}

[modify] https://crrev.com/ecf6be1dcf5f2fd0dd190742381d9dd52c0f3d26/chrome/common/extensions/api/_api_features.json

This bug requires manual review: We don't branch M60 until 2017-05-25.
Please contact the milestone owner if you have questions.
Owners: amineer@(Android), cmasso@(iOS), josafat@(ChromeOS), bustamante@(Desktop)

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

We haven't branched M60 yet, your change landed in time.

Did you mean to merge to 59?

Oh, sorry, was not paying attention there. No merging needed.