[chrome.dial] Don't fire event when getting an event from the network change notifier |
||||||||||
Issue descriptionVersion: ChromeOS 53 chrome.dial forces a deviceList event each time there is callback from the NetworkChangeNotifier. Because of Bug 644501 , this results in continuous Media Router wakeups on ChromeOS. This bug tracks a fix to not force-fire an event in this case.
,
Sep 14 2016
,
Sep 14 2016
Marking as RB-S for M-54 as well.
,
Sep 14 2016
is this RBS for M53? what devices is this being seen on?
,
Sep 14 2016
AFAIK it's not device-specific. It's a platform issue.
,
Sep 15 2016
Could you include a repro for this? Note: issue 644501 is not the root cause. Issue 647004 may have the same root cause however.
,
Sep 15 2016
,
Sep 15 2016
Inspecting the code, NetworkChangeNotifierChromeos only triggers an event when the default network changes, so I do not think that the connection manager is the cause here.
,
Sep 20 2016
I agree with c#8. I think the continuous wakeups are another side effect of how we manage event listeners in this API. However it's also not clear we want to always fire an event when we get a callback from the NetworkChangeNotifier.
,
Sep 21 2016
,
Sep 28 2016
,
May 10 2017
Next step is to scope the amount of work required w/o impacting other users.
,
May 10 2017
Given we are in the process of obsoleting this API, WontFix. |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by mfo...@chromium.org
, Sep 14 2016