Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(275)

Issue 2912323002: Mojo JS bindings: flip the default value of use_new_js_bindings to true. (Closed)

Created:
3 years, 6 months ago by junwei
Modified:
3 years, 6 months ago
Reviewers:
yzshen1, mtklein_C
CC:
chromium-reviews
Target Ref:
refs/heads/master
Project:
chromium
Visibility:
Public.

Description

Mojo JS bindings: flip the default value of use_new_js_bindings to true. Test cases will time out when CL [1] using skia mojo bitmap. [1] https://codereview.chromium.org/2875243002# BUG=699569 Review-Url: https://codereview.chromium.org/2912323002 Cr-Commit-Position: refs/heads/master@{#476555} Committed: https://chromium.googlesource.com/chromium/src/+/9821a80606c582307bc791c798c6ccaeadaa70ec

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+3 lines, -0 lines) Patch
M skia/public/interfaces/BUILD.gn View 1 chunk +3 lines, -0 lines 0 comments Download

Messages

Total messages: 37 (18 generated)
junwei
PTAL, thanks.
3 years, 6 months ago (2017-05-31 08:29:27 UTC) #2
yzshen1
Please consider switching the tests to use the new mode. :) LGTM
3 years, 6 months ago (2017-05-31 17:46:40 UTC) #3
junwei
On 2017/05/31 17:46:40, yzshen1 wrote: > Please consider switching the tests to use the new ...
3 years, 6 months ago (2017-06-01 02:36:07 UTC) #8
commit-bot: I haz the power
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.org/2912323002/1
3 years, 6 months ago (2017-06-01 02:36:51 UTC) #10
commit-bot: I haz the power
Try jobs failed on following builders: chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presubmit/builds/452847)
3 years, 6 months ago (2017-06-01 02:45:37 UTC) #12
commit-bot: I haz the power
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.org/2912323002/1
3 years, 6 months ago (2017-06-01 02:48:55 UTC) #14
junwei
3 years, 6 months ago (2017-06-01 02:57:45 UTC) #16
commit-bot: I haz the power
Try jobs failed on following builders: chromium_presubmit on master.tryserver.chromium.linux (JOB_FAILED, http://build.chromium.org/p/tryserver.chromium.linux/builders/chromium_presubmit/builds/452856)
3 years, 6 months ago (2017-06-01 02:58:21 UTC) #18
junwei
On 2017/06/01 02:58:21, commit-bot: I haz the power wrote: > Try jobs failed on following ...
3 years, 6 months ago (2017-06-02 00:29:04 UTC) #21
mtklein_C
¯\_(ツ)_/¯ lgtm
3 years, 6 months ago (2017-06-02 00:33:05 UTC) #23
commit-bot: I haz the power
CQ is trying da patch. Follow status at: https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.org/2912323002/1
3 years, 6 months ago (2017-06-02 00:48:18 UTC) #25
commit-bot: I haz the power
Committed patchset #1 (id:1) as https://chromium.googlesource.com/chromium/src/+/9821a80606c582307bc791c798c6ccaeadaa70ec
3 years, 6 months ago (2017-06-02 03:52:02 UTC) #28
yzshen1
On 2017/06/02 03:52:02, commit-bot: I haz the power wrote: > Committed patchset #1 (id:1) as ...
3 years, 6 months ago (2017-06-02 15:09:08 UTC) #29
junwei
On 2017/06/02 15:09:08, yzshen1 wrote: > On 2017/06/02 03:52:02, commit-bot: I haz the power wrote: ...
3 years, 6 months ago (2017-06-05 00:43:21 UTC) #30
junwei
On 2017/05/31 17:46:40, yzshen1 wrote: > Please consider switching the tests to use the new ...
3 years, 6 months ago (2017-06-07 08:13:07 UTC) #33
yzshen1
On 2017/06/07 08:13:07, junwei wrote: > On 2017/05/31 17:46:40, yzshen1 wrote: > > Please consider ...
3 years, 6 months ago (2017-06-07 16:47:42 UTC) #34
yzshen1
On 2017/06/07 16:47:42, yzshen1 wrote: > On 2017/06/07 08:13:07, junwei wrote: > > On 2017/05/31 ...
3 years, 6 months ago (2017-06-07 16:51:55 UTC) #35
junwei
On 2017/06/07 16:51:55, yzshen1 wrote: > On 2017/06/07 16:47:42, yzshen1 wrote: > > On 2017/06/07 ...
3 years, 6 months ago (2017-06-08 01:46:24 UTC) #36
yzshen1
3 years, 6 months ago (2017-06-08 17:35:15 UTC) #37
Message was sent while issue was closed.
On 2017/06/08 01:46:24, junwei wrote:
> On 2017/06/07 16:51:55, yzshen1 wrote:
> > On 2017/06/07 16:47:42, yzshen1 wrote:
> > > On 2017/06/07 08:13:07, junwei wrote:
> > > > On 2017/05/31 17:46:40, yzshen1 wrote:
> > > > > Please consider switching the tests to use the new mode. :)
> > > > > 
> > > > > LGTM
> > > > 
> > > > I am trying to switch shape detection layout tests to use new js
binding,
> > but
> > > > textdetection.mojom [1] is depend on geometry.mojom which still use old
js
> > > > binding, does it mean all of using geometry.mojom need to switch new js
> > > binding?
> > > > such as media/capture/mojo/BUILD.gn [2]
> > > 
> > > Thanks for looking into this!
> > > 
> > > If a mojom target depends on geometry.mojom, *and* this mojom target is
used
> > in
> > > JavaScript, then yes we need to switch this mojom target.
> > > If it is never used in JavaScript anywhere, then no.
> > > 
> > > Looking at media/capture/mojo/BUILD.gn:
> > > The "capture_types" target is already using the new mode (Because it
doesn't
> > > have use_new_js_bindings = false.) That probably means it is never used in
> > > JavaScript so we don't care the inconsistent between "capture_types" and
> > > "geometry".
> > 
> > I confirmed that "capture_types" is never used in JavaScript:
> >
>
https://cs.chromium.org/search/?q=file:(js%7Chtml)$+video_capture_types.mojom...
> > 
> > 
> > > 
> > > The "image_capture" target doesn't depend on "geometry", so it should be
> > > irrelevant to the problem we are discussing.
> > > 
> > > 
> > > > 
> > > > [1]
> > > >
> > >
> >
>
https://cs.chromium.org/chromium/src/services/shape_detection/public/interfac...
> > > > [2] https://cs.chromium.org/chromium/src/media/capture/mojo/BUILD.gn
> 
> I got it, thanks.
> 
> Loading mojo/public/js/bindings module switched to <script
> src="file:///gen/layout_test_data/mojo/public/js/mojo_bindings.js"></script>.
> How to use content/public/renderer/interfaces in new binding?

(I would suggest we discuss such issue on a separate mailing thread in the
future, since it is not directly related to this patch.)
Do you mean you need to use "addInterfaceOverrideForTesting"?

There is a new way doing this. Please see MojoInterfaceInterceptor in
//src/third_party/WebKit/LayoutTests/mojo/bind-interface.html

Powered by Google App Engine
This is Rietveld 408576698