Get discovery network info on creation for metrics

Comments

Get discovery network info on creation for metrics
Currently, DiscoveryNetworkMonitor attempts to be lazy and doesn't
require network info is gathered when it is first created. However,
since metrics are being collected by an observer, it's relevant for
network info to now be collected on creation of DiscoveryNetworkMonitor.
Bug: 698943
Change-Id: If1214e1a1a484d20ea029d3742142db54ec92104
Reviewed-on: https://chromium-review.googlesource.com/730413
Commit-Queue: Brandon Tolsch <btolsch@chromium.org>
Reviewed-by: Derek Cheng <imcheng@chromium.org>
Cr-Commit-Position: refs/heads/master@{#514190}

Initialize ATK bridge without atk-bridge GTK module on GTK3.

Comments

Initialize ATK bridge without atk-bridge GTK module on GTK3.
On GTK3, the atk-bridge.so GTK module is not expected to be available
as the policy is that accessibility support is always loaded. So
GTK initialization was already registering its own AtkMisc instance,
and the GTK ATK root node. This was the node associated to ATK bridge.
But Chromium needs to register its own ATK root node. So, for the
case of GTK3, ATK bridge should happen immediately after the
registration of Chromium AtkMisc instance, that will refer to
the proper ATK root node.
Bug: 780973
Change-Id: Iaed33530eb6a801ab2bec0a299d8c9b7fa091f5f
Reviewed-on: https://chromium-review.googlesource.com/753442
Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
Reviewed-by: Dominic Mazzoni <dmazzoni@chromium.org>
Reviewed-by: Elliot Glaysher <erg@chromium.org>
Reviewed-by: Dirk Pranke <dpranke@chromium.org>
Commit-Queue: José Dapena Paz <jose.dapena@lge.com>
Cr-Commit-Position: refs/heads/master@{#514191}