This launch bug has not been modified in the last 90 days and has no milestone label. Please take a look and add appropriate milestone label.

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

This launch bug has not been modified in the last 90 days and has no milestone label. Please take a look and add appropriate milestone label.

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

Updating launch bugs to convert to new launch process in go/newChromeFeature.  Automatically setting Launch-Exp-Leadership-NA since this appears to be a legacy technical / simple launch (all existing cross-functional bits are set to NA).  Note that in the new process, no review / approval for technical / simple launches is required (though please be sure you are confident there is no cross-functional impact here).  Contact amineer@ with any questions or concerns.

Updating launch bugs to convert to new launch process in go/newChromeFeature.  Automatically setting Launch-Leadership-NA since this appears to be a legacy technical / simple launch (all existing cross-functional bits are set to NA).  Note that in the new process, no review / approval for technical / simple launches is required (though please be sure you are confident there is no cross-functional impact here).  Contact amineer@ with any questions or concerns.

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

commit 0ef734f4659e2af652b6846e073be226cd11de6d
Author: Devlin Cronin <rdevlin.cronin@chromium.org>
Date: Thu Jun 21 15:53:50 2018

[Extensions Bindings] Add a fieldtrial testing config entry for native bindings

We're getting ready to roll extension bindings out to beta, so add a
fieldtrial testing config entry for the experiment to have it run by
default on the bots.

Bug: 763564

Change-Id: Ibdf83e16cbc10e4c62e2304cf14cd7c24377bc31
Reviewed-on: https://chromium-review.googlesource.com/1108192
Reviewed-by: Ilya Sherman <isherman@chromium.org>
Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#569277}
[modify] https://crrev.com/0ef734f4659e2af652b6846e073be226cd11de6d/chrome/browser/extensions/error_console/error_console_browsertest.cc
[modify] https://crrev.com/0ef734f4659e2af652b6846e073be226cd11de6d/testing/variations/fieldtrial_testing_config.json

Adding mstones.  This has been in dev/canary for quite awhile, and we're expanding to beta soon.  Since this is a simple launch, my understanding is that no further approvals are necessary.

Note: This no longer requires launch review under the new policies (since it is not user facing, and is just a technical refactoring).  Finch complains about not having approvals, so we need to either change this bug type or file a new one.  Let's see how the former goes...

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

commit f1a0dda91609a85a1e11c3b2a39c6fea46da4972
Author: Devlin Cronin <rdevlin.cronin@chromium.org>
Date: Wed Dec 19 03:32:38 2018

[Extensions] Enable NativeCrxBindings experiment by default

Bug: 763564
Change-Id: I94722f68b79e89c8517caa6b402267f3dda5ea52
Reviewed-on: https://chromium-review.googlesource.com/c/1376740
Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org>
Commit-Queue: Devlin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/master@{#617720}
[modify] https://crrev.com/f1a0dda91609a85a1e11c3b2a39c6fea46da4972/extensions/common/extension_features.cc
[modify] https://crrev.com/f1a0dda91609a85a1e11c3b2a39c6fea46da4972/extensions/test/data/api_test/printer_provider/request_capability/test.js
[modify] https://crrev.com/f1a0dda91609a85a1e11c3b2a39c6fea46da4972/extensions/test/data/api_test/printer_provider/request_printers/test.js

Setting defect without priority to Pri-2.