On 2016/10/26 00:43:18, David Trainor wrote:
> Should we just remove the visibility if it's meant to be hit by all embedders?
Actually this target is only for chrome, because in core/resources:strings, we
do special things for enable_blimp_client flag, and the flag is only for chrome.
Added another target in here for blimp/client/app.
David Trainor- moved to gerrit
2016/10/28 04:20:08
Why is it only for chrome? We have to set enable_
On 2016/10/26 21:14:42, xingliu wrote:
> On 2016/10/26 00:43:18, David Trainor wrote:
> > Should we just remove the visibility if it's meant to be hit by all
embedders?
>
> Actually this target is only for chrome, because in core/resources:strings, we
> do special things for enable_blimp_client flag, and the flag is only for
chrome.
>
> Added another target in here for blimp/client/app.
Why is it only for chrome? We have to set enable_blimp_client for any embedder
right?
xingliu
2016/10/28 22:50:31
Yes, but for blimp_shell it's directly depend on c
On 2016/10/28 04:20:08, David Trainor (OOO to oct 31) wrote:
> On 2016/10/26 21:14:42, xingliu wrote:
> > On 2016/10/26 00:43:18, David Trainor wrote:
> > > Should we just remove the visibility if it's meant to be hit by all
> embedders?
> >
> > Actually this target is only for chrome, because in core/resources:strings,
we
> > do special things for enable_blimp_client flag, and the flag is only for
> chrome.
> >
> > Added another target in here for blimp/client/app.
>
> Why is it only for chrome? We have to set enable_blimp_client for any
embedder
> right?
Yes, but for blimp_shell it's directly depend on core/*, so if we let it go
through the target that checks |enable_blimp_client|, it might hit the scenario
that it didn't load the string but try to access the string.
Issue 2431653004: Setup Blimp internal string resources.
(Closed)
Created 4 years, 2 months ago by xingliu
Modified 4 years, 1 month ago
Reviewers: David Trainor- moved to gerrit, Nico
Base URL:
Comments: 12