Once crbug.com/663427 is resolved we'll be using the NotificationJobService to handle notification clicks (and closes) on Android N and above.
We ask Android to execute our jobs immediately (override deadline of 0ms), but we should add UMA to check in case this actually introduces a noticeable lag.
(Note there is already a noticeable lag if Chrome is killed when a notification is clicked and we have to start up the whole browser process.. this is just to check we're not introducing further lag)
Once http://crbug.com/663427 is resolved we'll be using the NotificationJobService to handle notification clicks (and closes) on Android N and above.
We ask Android to execute our jobs immediately (override deadline of 0ms), but we should add UMA to check in case this actually introduces a noticeable lag.
(Note there is already a noticeable lag if Chrome is killed when a notification is clicked and we have to start up the whole browser process.. this is just to check we're not introducing further lag)
Comment 1 by awdf@chromium.org
, Jan 25 2017