Componentize safe_browsing [X+1] : move the renderer part to component.

Componentize safe_browsing [X+1] : move the renderer part to component.

WIP: do not submit yet

This patch moves the chrome/renderer/safe_browsing/ code to component.
As a side-effect this enables support for threat reporting functionality
for embedders like Android WebView.

NOTE:
work in progress, depends on patch for moving protos

BUG=488675

[timvolodine, 2017-02-03 02:50:46]

timvolodine@chromium.org changed reviewers:
+ nparker@chromium.org, vakh@chromium.org

[timvolodine, 2017-02-03 02:50:47]

FYI for now, currently work in progress, but coming soon...

+owners: nparker@,vakh@
+cc:sgurun@,tobiasjs@

[sgurun-gerrit only, 2017-02-03 03:15:42]

On 2017/02/03 02:50:47, timvolodine wrote:
> FYI for now, currently work in progress, but coming soon...
> 
> +owners: nparker@,vakh@
> +cc:sgurun@,tobiasjs@

Tim are you sure this is needed for webview reporting? 

We do not want to have client side reporting in Android webview (and not in
chrome on android too).

Let's have a design document first to discuss.

[vakh (use Gerrit instead), 2017-02-14 00:14:08]

On 2017/02/03 03:15:42, sgurun wrote:
> On 2017/02/03 02:50:47, timvolodine wrote:
> > FYI for now, currently work in progress, but coming soon...
> > 
> > +owners: nparker@,vakh@
> > +cc:sgurun@,tobiasjs@
> 
> Tim are you sure this is needed for webview reporting? 
> 
> We do not want to have client side reporting in Android webview (and not in
> chrome on android too).
> 
> Let's have a design document first to discuss.

I'm going to move nparker@ and myself to CC on this CL.
Please move us back to the reviewers list when it is ready for review.

[vakh (use Gerrit instead), 2017-02-14 00:14:23]

vakh@chromium.org changed reviewers:
- nparker@chromium.org

[timvolodine, 2017-03-10 13:21:04]

On 2017/02/03 03:15:42, sgurun wrote:
> On 2017/02/03 02:50:47, timvolodine wrote:
> > FYI for now, currently work in progress, but coming soon...
> > 
> > +owners: nparker@,vakh@
> > +cc:sgurun@,tobiasjs@
> 
> Tim are you sure this is needed for webview reporting? 
> 
> We do not want to have client side reporting in Android webview (and not in
> chrome on android too).
> 
> Let's have a design document first to discuss.

As discussed offline this would be needed for the reporting functionality in
WebView. This patch depends on moving of protos:
https://codereview.chromium.org/2743563006/, will rebase and follow-up here and
once it lands.

[Jialiu Lin, 2017-03-10 19:11:36]

Description was changed from

==========
Componentize safe_browsing [X+1] : move the renderer part to component.

WIP: do not submit yet

This patch moves the chrome/renderer/safe_browsing/ code to component.
As a side-effect this enables support for threat reporting functionality
for embedders like Android WebView.

NOTE:
work in progress, depends on patch for moving protos

BUG=488675
==========

to

==========
Componentize safe_browsing [X+1] : move the renderer part to component.

WIP: do not submit yet

This patch moves the chrome/renderer/safe_browsing/ code to component.
As a side-effect this enables support for threat reporting functionality
for embedders like Android WebView.

NOTE:
work in progress, depends on patch for moving protos

BUG=488675
==========

[Jialiu Lin, 2017-03-10 19:11:36]

jialiul@chromium.org changed reviewers:
+ jialiul@chromium.org
- vakh@chromium.org