No one is using the aUseTrackingProtection parameter and also tracking
protection related preference in Classify API. And we shouldn't use it
that way in the future.
Differential Revision: https://phabricator.services.mozilla.com/D16798
--HG--
extra : moz-landing-system : lando
The crash happens when parent process tries to send classify result to
the content process while the IPC connection is already closed.
The only case that we needs IPC for classification is for Flash classification, but flash
classification is moved to parent process after Bug 1514202.
Although right now there is no consumer for the IPC version of
nsUrlClassifierDBService::AsyncClassifyLocalWithFeatures, we should
still fix this bug.
Differential Revision: https://phabricator.services.mozilla.com/D16362
--HG--
extra : moz-landing-system : lando
We add a new "on-off" protocol PURLClassifierLocal which calls
nsIURIClassifier.asyncClassifyLocalWithTables on construction and
calls back on destruction. Pretty much the same design as PURLClassifier.
In order to avoid code duplication, the actor implementation is templatized
and |MaybeInfo| in PURLClassifier.ipdl is moved around.
Test case is included and the custom event target is not in place for labelling.
The custom event target will be done in Bug 1353701.
MozReview-Commit-ID: IdHYgdnBV7S
--HG--
extra : rebase_source : ab1c896305b9f76cab13a92c9bd88c2d356aacb7
Dimi Lee
Andrea Marchesini
Sylvestre Ledru
Henry Chang
Thomas Nguyen
Ehsan Akhgari
Wes Kocher
Phil Ringnalda