Made the NavigationTracingObserver always be active whenever background tracing is active

Made the NavigationTracingObserver always be active whenever background tracing is active

This is needed so navigation tracing triggers can be used for any scenario, not just when --enable-navigation-tracing is set.

R=shatch,fmeawad

Committed: https://crrev.com/537726002122ef050257948da5bd8e1b977ff8aa
Cr-Commit-Position: refs/heads/master@{#357456}

[oystein (OOO til 10th of July), 2015-10-30 21:52:41]

Description was changed from

==========
Formatting


Buildfix


Made the NavigationTracingObserver always be active whenever background tracing
is active

BUG=
==========

to

==========
Made the NavigationTracingObserver always be active whenever background tracing
is active

R=shatch,fmeawad
==========

[oystein (OOO til 10th of July), 2015-10-30 21:52:41]

oysteine@chromium.org changed reviewers:
+ fmeawad@chromium.org, simonhatch@chromium.org

[oystein (OOO til 10th of July), 2015-10-30 21:53:03]

ptal!

[oystein (OOO til 10th of July), 2015-10-30 21:54:00]

Description was changed from

==========
Made the NavigationTracingObserver always be active whenever background tracing
is active

R=shatch,fmeawad
==========

to

==========
Made the NavigationTracingObserver always be active whenever background tracing
is active

This is needed so navigation tracing triggers can be used for any scenario, not
just when --enable-navigation-tracing is set.

R=shatch,fmeawad
==========

[fmeawad, 2015-10-30 22:57:21]

On 2015/10/30 21:53:03, Oystein wrote:
> ptal!

Does this mean it will trigger but with no listener?

[oystein (OOO til 10th of July), 2015-10-30 23:06:19]

On 2015/10/30 22:57:21, fmeawad wrote:
> On 2015/10/30 21:53:03, Oystein wrote:
> > ptal!
> 
> Does this mean it will trigger but with no listener?

When there's a scenario active but which doesn't have a rule listening for
navigation triggers, yep. For everyone without background tracing enabled it'll
still be disabled.

[shatch, 2015-11-02 15:00:16]

lgtm

[oystein (OOO til 10th of July), 2015-11-02 18:10:23]

oysteine@chromium.org changed reviewers:
+ sky@chromium.org

[oystein (OOO til 10th of July), 2015-11-02 18:10:38]

+sky for chrome/browser/ui, ptal! :)

[oystein (OOO til 10th of July), 2015-11-02 18:11:09]

oysteine@chromium.org changed reviewers:
+ sievers@chromium.org

[oystein (OOO til 10th of July), 2015-11-02 18:11:33]

+sievers for content/public

[fmeawad, 2015-11-02 18:58:32]

On 2015/11/02 18:11:33, Oystein wrote:
> +sievers for content/public

lgtm

[fmeawad, 2015-11-02 18:58:35]

On 2015/11/02 18:11:33, Oystein wrote:
> +sievers for content/public

lgtm

[no sievers, 2015-11-02 18:58:55]

On 2015/11/02 18:11:33, Oystein wrote:
> +sievers for content/public

lgtm

[sky, 2015-11-02 20:24:57]

LGTM

[oystein (OOO til 10th of July), 2015-11-02 20:43:29]

The CQ bit was checked by oysteine@chromium.org

[commit-bot: I haz the power, 2015-11-02 20:45:00]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1426803004/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/1426803004/1

[commit-bot: I haz the power, 2015-11-02 22:41:34]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-11-02 22:42:55]

Patchset 1 (id:??) landed as
https://crrev.com/537726002122ef050257948da5bd8e1b977ff8aa
Cr-Commit-Position: refs/heads/master@{#357456}