Enable deep-linking from notifications for recently used web apps on the Android home screen.

Enable deep-linking from notifications for recently used web apps on the Android home screen.

This CL permits notifications pointing to a recently used,
standalone-capable web app on the Android home screen to open in the
standalone web frame.

The web app must be added to home screen, capable of opening in
standalone mode, and have been opened from the home screen within the
last ten days. If any of these conditions are not met, the notification
will fall back to the existing behaviour.

The search for a matching web app is conducted by comparing the URL
which the notification is asking to be opened with the scope of all web
apps known to Chromium. The scope for a web app is its URL, minus the
final component of its path, any query parameters, and any fragments.
A future CL will implement the manifest scope property, which will
replace this estimated scope. The web app with the longest scope that
matches the URL to be opened is chosen.

Additional tests for the scoped search are added in this CL. A new
shortcut source is added to indicate launches from a notification, and
the WebappRegistry is updated to not change the last updated time of web
app data which has not been opened from the home screen. This is
necessary to ensure web apps cannot spam the user with notifications to
update their last used time and hence how long Chromium will cache their
app data.

BUG=541711, 594872
R=dfalcantara

Committed: https://crrev.com/1ce7d2f020a7452bd0399dd50e4580981deeb4dd
Cr-Commit-Position: refs/heads/master@{#385967}

[dominickn, 2016-04-06 13:07:02]

And here's number 3. PTAL, thanks!

https://codereview.chromium.org/1867543002/diff/20001/chrome/android/junit/sr...
File
chrome/android/junit/src/org/chromium/chrome/browser/webapps/WebappRegistryTest.java
(left):

https://codereview.chromium.org/1867543002/diff/20001/chrome/android/junit/sr...
chrome/android/junit/src/org/chromium/chrome/browser/webapps/WebappRegistryTest.java:120:
long before = System.currentTimeMillis();
The before check started being flaky for me, so I just made it an after check.

[gone, 2016-04-07 19:10:45]

lgtm

Not seeing any red flags, anyway.

https://chromiumcodereview.appspot.com/1867543002/diff/20001/chrome/android/j...
File
chrome/android/java/src/org/chromium/chrome/browser/ChromeServiceTabLauncher.java
(right):

https://chromiumcodereview.appspot.com/1867543002/diff/20001/chrome/android/j...
chrome/android/java/src/org/chromium/chrome/browser/ChromeServiceTabLauncher.java:43:
new WebappRegistry.FetchWebappDataStorageCallback() {
To avoid the extra indentation, could you create the callback outside of the
function call?

https://chromiumcodereview.appspot.com/1867543002/diff/20001/chrome/android/j...
File
chrome/android/java/src/org/chromium/chrome/browser/webapps/WebappActivity.java
(right):

https://chromiumcodereview.appspot.com/1867543002/diff/20001/chrome/android/j...
chrome/android/java/src/org/chromium/chrome/browser/webapps/WebappActivity.java:268:
// launched from home screen.
nit: Maybe comment here about why?  Not wanting to mess with our heuristics for
guessing about whether something is still on the home screen makes sense for me,
but whoever follows might not understand the nuance.

https://chromiumcodereview.appspot.com/1867543002/diff/20001/chrome/android/j...
File
chrome/android/java/src/org/chromium/chrome/browser/webapps/WebappDataStorage.java
(right):

https://chromiumcodereview.appspot.com/1867543002/diff/20001/chrome/android/j...
chrome/android/java/src/org/chromium/chrome/browser/webapps/WebappDataStorage.java:175:
// removed. Otherwise, the next launch from homescreen will update the last used
time.
home screen, here and everywhere else

https://chromiumcodereview.appspot.com/1867543002/diff/20001/chrome/android/j...
chrome/android/java/src/org/chromium/chrome/browser/webapps/WebappDataStorage.java:177:
openSharedPreferences(context, webappId).edit().putLong(KEY_LAST_USED,
LAST_USED_UNSET)
At this point, should the sharedPreferences just be stored temporarily and then
each of the removals or changes should be put into their own lines?  It's kind
of weird to parse.

https://chromiumcodereview.appspot.com/1867543002/diff/20001/chrome/android/j...
chrome/android/java/src/org/chromium/chrome/browser/webapps/WebappDataStorage.java:364:
* Returns true if this web app has been launched from homescreen recently
(within 10 days).
This seems like a comment that'll go out of sync quickly.  Maybe refer to
WEBAPP_LAST_OPEN_MAX_TIME instead?

https://chromiumcodereview.appspot.com/1867543002/diff/20001/chrome/android/j...
File chrome/android/java/src/org/chromium/chrome/browser/webapps/WebappInfo.java
(right):

https://chromiumcodereview.appspot.com/1867543002/diff/20001/chrome/android/j...
chrome/android/java/src/org/chromium/chrome/browser/webapps/WebappInfo.java:261:
* homescreen (as opposed to an intent from a push notification or other internal
source).
Returns true if the WebappInfo was created for an Intent fired from a launcher
shortcut (as opposed to blah....)

https://chromiumcodereview.appspot.com/1867543002/diff/20001/chrome/android/j...
chrome/android/java/src/org/chromium/chrome/browser/webapps/WebappInfo.java:263:
public boolean launchedFromHomescreen() {
nit: isLaunchedFromHomeScreen()?

https://chromiumcodereview.appspot.com/1867543002/diff/20001/chrome/android/j...
File
chrome/android/java/src/org/chromium/chrome/browser/webapps/WebappLauncherActivity.java
(right):

https://chromiumcodereview.appspot.com/1867543002/diff/20001/chrome/android/j...
chrome/android/java/src/org/chromium/chrome/browser/webapps/WebappLauncherActivity.java:63:
ApplicationStatus.getApplicationContext());
Indentation is wonky here (indent by 8 then 4).  Would be nice if you could pull
out the second half of the conditional, but I'm not sure how to do it nicely.

https://chromiumcodereview.appspot.com/1867543002/diff/20001/chrome/android/j...
File
chrome/android/junit/src/org/chromium/chrome/browser/webapps/WebappDataStorageTest.java
(right):

https://chromiumcodereview.appspot.com/1867543002/diff/20001/chrome/android/j...
chrome/android/junit/src/org/chromium/chrome/browser/webapps/WebappDataStorageTest.java:238:
// Mark as launched
nit: launched.

https://chromiumcodereview.appspot.com/1867543002/diff/20001/chrome/android/j...
File
chrome/android/junit/src/org/chromium/chrome/browser/webapps/WebappRegistryTest.java
(right):

https://chromiumcodereview.appspot.com/1867543002/diff/20001/chrome/android/j...
chrome/android/junit/src/org/chromium/chrome/browser/webapps/WebappRegistryTest.java:95:
mCallbackCalled = true;
This really should be a member variable of this callback class, at this point. 
It'll be too easy to accidentally have one class accidentally affect another
test otherwise.

https://chromiumcodereview.appspot.com/1867543002/diff/20001/chrome/android/j...
chrome/android/junit/src/org/chromium/chrome/browser/webapps/WebappRegistryTest.java:155:
assertTrue(!launched);
can't just assertTrue(!webAppPref....) here?

https://chromiumcodereview.appspot.com/1867543002/diff/20001/chrome/android/j...
chrome/android/junit/src/org/chromium/chrome/browser/webapps/WebappRegistryTest.java:492:
public void testGetWebappDataStorageForUrl() throws Exception {
Can you add comments here?  I'm not sure what I'm looking at.

[dominickn, 2016-04-07 22:59:59]

Description was changed from

==========
Enable deep-linking from notifications for recently used web apps on the Android
homescreen.

This CL permits notifications pointing to a recently used,
standalone-capable web app on the Android homescreen to open in the
standalone web frame.

The web app must be added to homescreen, capable of opening in
standalone mode, and have been opened from the homescreen within the
last ten days. If any of these conditions are not met, the notification
will fall back to the existing behaviour.

The search for a matching web app is conducted by comparing the URL
which the notification is asking to be opened with the scope of all web
apps known to Chromium. The scope for a web app is its URL, minus the
final component of its path, any query parameters, and any fragments.
A future CL will implement the manifest scope property, which will
replace this estimated scope. The web app with the longest scope that
matches the URL to be opened is chosen.

Additional tests for the scoped search are added in this CL. A new
shortcut source is added to indicate launches from a notification, and
the WebappRegistry is updated to not change the last updated time of web
app data which has not been opened from the homescreen. This is
necessary to ensure web apps cannot spam the user with notifications to
update their last used time and hence how long Chromium will cache their
app data.

BUG=541711,594872
R=dfalcantara
==========

to

==========
Enable deep-linking from notifications for recently used web apps on the Android
homescreen.

This CL permits notifications pointing to a recently used,
standalone-capable web app on the Android homescreen to open in the
standalone web frame.

The web app must be added to homescreen, capable of opening in
standalone mode, and have been opened from the homescreen within the
last ten days. If any of these conditions are not met, the notification
will fall back to the existing behaviour.

The search for a matching web app is conducted by comparing the URL
which the notification is asking to be opened with the scope of all web
apps known to Chromium. The scope for a web app is its URL, minus the
final component of its path, any query parameters, and any fragments.
A future CL will implement the manifest scope property, which will
replace this estimated scope. The web app with the longest scope that
matches the URL to be opened is chosen.

Additional tests for the scoped search are added in this CL. A new
shortcut source is added to indicate launches from a notification, and
the WebappRegistry is updated to not change the last updated time of web
app data which has not been opened from the homescreen. This is
necessary to ensure web apps cannot spam the user with notifications to
update their last used time and hence how long Chromium will cache their
app data.

BUG=541711,594872
R=dfalcantara
==========

[dominickn, 2016-04-07 22:59:59]

dominickn@chromium.org changed reviewers:
+ isherman@chromium.org

[dominickn, 2016-04-07 23:01:43]

Thanks!

+isherman: PTAL at the minor change in histograms.xml (adding a new enum value
and modifying a description)

[Ilya Sherman, 2016-04-07 23:37:41]

histograms.xml lgtm

[dominickn, 2016-04-08 01:08:15]

Description was changed from

==========
Enable deep-linking from notifications for recently used web apps on the Android
homescreen.

This CL permits notifications pointing to a recently used,
standalone-capable web app on the Android homescreen to open in the
standalone web frame.

The web app must be added to homescreen, capable of opening in
standalone mode, and have been opened from the homescreen within the
last ten days. If any of these conditions are not met, the notification
will fall back to the existing behaviour.

The search for a matching web app is conducted by comparing the URL
which the notification is asking to be opened with the scope of all web
apps known to Chromium. The scope for a web app is its URL, minus the
final component of its path, any query parameters, and any fragments.
A future CL will implement the manifest scope property, which will
replace this estimated scope. The web app with the longest scope that
matches the URL to be opened is chosen.

Additional tests for the scoped search are added in this CL. A new
shortcut source is added to indicate launches from a notification, and
the WebappRegistry is updated to not change the last updated time of web
app data which has not been opened from the homescreen. This is
necessary to ensure web apps cannot spam the user with notifications to
update their last used time and hence how long Chromium will cache their
app data.

BUG=541711,594872
R=dfalcantara
==========

to

==========
Enable deep-linking from notifications for recently used web apps on the Android
home screen.

This CL permits notifications pointing to a recently used,
standalone-capable web app on the Android home screen to open in the
standalone web frame.

The web app must be added to home screen, capable of opening in
standalone mode, and have been opened from the home screen within the
last ten days. If any of these conditions are not met, the notification
will fall back to the existing behaviour.

The search for a matching web app is conducted by comparing the URL
which the notification is asking to be opened with the scope of all web
apps known to Chromium. The scope for a web app is its URL, minus the
final component of its path, any query parameters, and any fragments.
A future CL will implement the manifest scope property, which will
replace this estimated scope. The web app with the longest scope that
matches the URL to be opened is chosen.

Additional tests for the scoped search are added in this CL. A new
shortcut source is added to indicate launches from a notification, and
the WebappRegistry is updated to not change the last updated time of web
app data which has not been opened from the home screen. This is
necessary to ensure web apps cannot spam the user with notifications to
update their last used time and hence how long Chromium will cache their
app data.

BUG=541711,594872
R=dfalcantara
==========

[dominickn, 2016-04-08 01:10:46]

Thanks!

https://codereview.chromium.org/1867543002/diff/20001/chrome/android/java/src...
File
chrome/android/java/src/org/chromium/chrome/browser/ChromeServiceTabLauncher.java
(right):

https://codereview.chromium.org/1867543002/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/ChromeServiceTabLauncher.java:43:
new WebappRegistry.FetchWebappDataStorageCallback() {
On 2016/04/07 19:10:44, dfalcantara wrote:
> To avoid the extra indentation, could you create the callback outside of the
> function call?

Done.

https://codereview.chromium.org/1867543002/diff/20001/chrome/android/java/src...
File
chrome/android/java/src/org/chromium/chrome/browser/webapps/WebappActivity.java
(right):

https://codereview.chromium.org/1867543002/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/webapps/WebappActivity.java:268:
// launched from home screen.
On 2016/04/07 19:10:44, dfalcantara wrote:
> nit: Maybe comment here about why?  Not wanting to mess with our heuristics
for
> guessing about whether something is still on the home screen makes sense for
me,
> but whoever follows might not understand the nuance.

Done.

https://codereview.chromium.org/1867543002/diff/20001/chrome/android/java/src...
File
chrome/android/java/src/org/chromium/chrome/browser/webapps/WebappDataStorage.java
(right):

https://codereview.chromium.org/1867543002/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/webapps/WebappDataStorage.java:175:
// removed. Otherwise, the next launch from homescreen will update the last used
time.
On 2016/04/07 19:10:44, dfalcantara wrote:
> home screen, here and everywhere else

Done.

https://codereview.chromium.org/1867543002/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/webapps/WebappDataStorage.java:177:
openSharedPreferences(context, webappId).edit().putLong(KEY_LAST_USED,
LAST_USED_UNSET)
On 2016/04/07 19:10:44, dfalcantara wrote:
> At this point, should the sharedPreferences just be stored temporarily and
then
> each of the removals or changes should be put into their own lines?  It's kind
> of weird to parse.

Done.

https://codereview.chromium.org/1867543002/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/webapps/WebappDataStorage.java:364:
* Returns true if this web app has been launched from homescreen recently
(within 10 days).
On 2016/04/07 19:10:44, dfalcantara wrote:
> This seems like a comment that'll go out of sync quickly.  Maybe refer to
> WEBAPP_LAST_OPEN_MAX_TIME instead?

Done.

https://codereview.chromium.org/1867543002/diff/20001/chrome/android/java/src...
File chrome/android/java/src/org/chromium/chrome/browser/webapps/WebappInfo.java
(right):

https://codereview.chromium.org/1867543002/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/webapps/WebappInfo.java:261:
* homescreen (as opposed to an intent from a push notification or other internal
source).
On 2016/04/07 19:10:44, dfalcantara wrote:
> Returns true if the WebappInfo was created for an Intent fired from a launcher
> shortcut (as opposed to blah....)

Done.

https://codereview.chromium.org/1867543002/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/webapps/WebappInfo.java:263:
public boolean launchedFromHomescreen() {
On 2016/04/07 19:10:44, dfalcantara wrote:
> nit: isLaunchedFromHomeScreen()?

Done.

https://codereview.chromium.org/1867543002/diff/20001/chrome/android/java/src...
File
chrome/android/java/src/org/chromium/chrome/browser/webapps/WebappLauncherActivity.java
(right):

https://codereview.chromium.org/1867543002/diff/20001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/webapps/WebappLauncherActivity.java:63:
ApplicationStatus.getApplicationContext());
On 2016/04/07 19:10:44, dfalcantara wrote:
> Indentation is wonky here (indent by 8 then 4).  Would be nice if you could
pull
> out the second half of the conditional, but I'm not sure how to do it nicely.

I just used another variable. Seems a bit nicer this way rather than having the
huge conditional.

https://codereview.chromium.org/1867543002/diff/20001/chrome/android/junit/sr...
File
chrome/android/junit/src/org/chromium/chrome/browser/webapps/WebappDataStorageTest.java
(right):

https://codereview.chromium.org/1867543002/diff/20001/chrome/android/junit/sr...
chrome/android/junit/src/org/chromium/chrome/browser/webapps/WebappDataStorageTest.java:238:
// Mark as launched
On 2016/04/07 19:10:44, dfalcantara wrote:
> nit: launched.

Done.

https://codereview.chromium.org/1867543002/diff/20001/chrome/android/junit/sr...
File
chrome/android/junit/src/org/chromium/chrome/browser/webapps/WebappRegistryTest.java
(right):

https://codereview.chromium.org/1867543002/diff/20001/chrome/android/junit/sr...
chrome/android/junit/src/org/chromium/chrome/browser/webapps/WebappRegistryTest.java:95:
mCallbackCalled = true;
On 2016/04/07 19:10:44, dfalcantara wrote:
> This really should be a member variable of this callback class, at this point.

> It'll be too easy to accidentally have one class accidentally affect another
> test otherwise.

Done.

https://codereview.chromium.org/1867543002/diff/20001/chrome/android/junit/sr...
chrome/android/junit/src/org/chromium/chrome/browser/webapps/WebappRegistryTest.java:155:
assertTrue(!launched);
On 2016/04/07 19:10:45, dfalcantara wrote:
> can't just assertTrue(!webAppPref....) here?

Done.

https://codereview.chromium.org/1867543002/diff/20001/chrome/android/junit/sr...
chrome/android/junit/src/org/chromium/chrome/browser/webapps/WebappRegistryTest.java:492:
public void testGetWebappDataStorageForUrl() throws Exception {
On 2016/04/07 19:10:45, dfalcantara wrote:
> Can you add comments here?  I'm not sure what I'm looking at.

Done.

[gone, 2016-04-08 01:14:07]

re-lgtm % nits

https://codereview.chromium.org/1867543002/diff/40001/chrome/android/java/src...
File
chrome/android/java/src/org/chromium/chrome/browser/ChromeServiceTabLauncher.java
(right):

https://codereview.chromium.org/1867543002/diff/40001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/ChromeServiceTabLauncher.java:73:
// The URL is within the scope of a recently launched standalone-capable
nit: reindent all the things

https://codereview.chromium.org/1867543002/diff/40001/chrome/android/java/src...
File chrome/android/java/src/org/chromium/chrome/browser/webapps/WebappInfo.java
(right):

https://codereview.chromium.org/1867543002/diff/40001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/webapps/WebappInfo.java:263:
public boolean islaunchedFromHomescreen() {
nit: isLaunchedFromHomeScreen (isl)

[dominickn, 2016-04-08 02:58:36]

The CQ bit was checked by dominickn@chromium.org

[dominickn, 2016-04-08 02:58:36]

The patchset sent to the CQ was uploaded after l-g-t-m from
isherman@chromium.org, dfalcantara@chromium.org
Link to the patchset: https://codereview.chromium.org/1867543002/#ps60001
(title: "Address nits")

[dominickn, 2016-04-08 02:58:45]

Thanks!

https://codereview.chromium.org/1867543002/diff/40001/chrome/android/java/src...
File
chrome/android/java/src/org/chromium/chrome/browser/ChromeServiceTabLauncher.java
(right):

https://codereview.chromium.org/1867543002/diff/40001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/ChromeServiceTabLauncher.java:73:
// The URL is within the scope of a recently launched standalone-capable
On 2016/04/08 01:14:07, dfalcantara wrote:
> nit: reindent all the things

Done.

https://codereview.chromium.org/1867543002/diff/40001/chrome/android/java/src...
File chrome/android/java/src/org/chromium/chrome/browser/webapps/WebappInfo.java
(right):

https://codereview.chromium.org/1867543002/diff/40001/chrome/android/java/src...
chrome/android/java/src/org/chromium/chrome/browser/webapps/WebappInfo.java:263:
public boolean islaunchedFromHomescreen() {
On 2016/04/08 01:14:07, dfalcantara wrote:
> nit: isLaunchedFromHomeScreen (isl)

Done.

[commit-bot: I haz the power, 2016-04-08 02:59:41]

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

[commit-bot: I haz the power, 2016-04-08 03:10:13]

Description was changed from

==========
Enable deep-linking from notifications for recently used web apps on the Android
home screen.

This CL permits notifications pointing to a recently used,
standalone-capable web app on the Android home screen to open in the
standalone web frame.

The web app must be added to home screen, capable of opening in
standalone mode, and have been opened from the home screen within the
last ten days. If any of these conditions are not met, the notification
will fall back to the existing behaviour.

The search for a matching web app is conducted by comparing the URL
which the notification is asking to be opened with the scope of all web
apps known to Chromium. The scope for a web app is its URL, minus the
final component of its path, any query parameters, and any fragments.
A future CL will implement the manifest scope property, which will
replace this estimated scope. The web app with the longest scope that
matches the URL to be opened is chosen.

Additional tests for the scoped search are added in this CL. A new
shortcut source is added to indicate launches from a notification, and
the WebappRegistry is updated to not change the last updated time of web
app data which has not been opened from the home screen. This is
necessary to ensure web apps cannot spam the user with notifications to
update their last used time and hence how long Chromium will cache their
app data.

BUG=541711,594872
R=dfalcantara
==========

to

==========
Enable deep-linking from notifications for recently used web apps on the Android
home screen.

This CL permits notifications pointing to a recently used,
standalone-capable web app on the Android home screen to open in the
standalone web frame.

The web app must be added to home screen, capable of opening in
standalone mode, and have been opened from the home screen within the
last ten days. If any of these conditions are not met, the notification
will fall back to the existing behaviour.

The search for a matching web app is conducted by comparing the URL
which the notification is asking to be opened with the scope of all web
apps known to Chromium. The scope for a web app is its URL, minus the
final component of its path, any query parameters, and any fragments.
A future CL will implement the manifest scope property, which will
replace this estimated scope. The web app with the longest scope that
matches the URL to be opened is chosen.

Additional tests for the scoped search are added in this CL. A new
shortcut source is added to indicate launches from a notification, and
the WebappRegistry is updated to not change the last updated time of web
app data which has not been opened from the home screen. This is
necessary to ensure web apps cannot spam the user with notifications to
update their last used time and hence how long Chromium will cache their
app data.

BUG=541711,594872
R=dfalcantara
==========

[commit-bot: I haz the power, 2016-04-08 03:10:15]

Committed patchset #4 (id:60001)

[commit-bot: I haz the power, 2016-04-08 03:12:03]

Description was changed from

==========
Enable deep-linking from notifications for recently used web apps on the Android
home screen.

This CL permits notifications pointing to a recently used,
standalone-capable web app on the Android home screen to open in the
standalone web frame.

The web app must be added to home screen, capable of opening in
standalone mode, and have been opened from the home screen within the
last ten days. If any of these conditions are not met, the notification
will fall back to the existing behaviour.

The search for a matching web app is conducted by comparing the URL
which the notification is asking to be opened with the scope of all web
apps known to Chromium. The scope for a web app is its URL, minus the
final component of its path, any query parameters, and any fragments.
A future CL will implement the manifest scope property, which will
replace this estimated scope. The web app with the longest scope that
matches the URL to be opened is chosen.

Additional tests for the scoped search are added in this CL. A new
shortcut source is added to indicate launches from a notification, and
the WebappRegistry is updated to not change the last updated time of web
app data which has not been opened from the home screen. This is
necessary to ensure web apps cannot spam the user with notifications to
update their last used time and hence how long Chromium will cache their
app data.

BUG=541711,594872
R=dfalcantara
==========

to

==========
Enable deep-linking from notifications for recently used web apps on the Android
home screen.

This CL permits notifications pointing to a recently used,
standalone-capable web app on the Android home screen to open in the
standalone web frame.

The web app must be added to home screen, capable of opening in
standalone mode, and have been opened from the home screen within the
last ten days. If any of these conditions are not met, the notification
will fall back to the existing behaviour.

The search for a matching web app is conducted by comparing the URL
which the notification is asking to be opened with the scope of all web
apps known to Chromium. The scope for a web app is its URL, minus the
final component of its path, any query parameters, and any fragments.
A future CL will implement the manifest scope property, which will
replace this estimated scope. The web app with the longest scope that
matches the URL to be opened is chosen.

Additional tests for the scoped search are added in this CL. A new
shortcut source is added to indicate launches from a notification, and
the WebappRegistry is updated to not change the last updated time of web
app data which has not been opened from the home screen. This is
necessary to ensure web apps cannot spam the user with notifications to
update their last used time and hence how long Chromium will cache their
app data.

BUG=541711,594872
R=dfalcantara

Committed: https://crrev.com/1ce7d2f020a7452bd0399dd50e4580981deeb4dd
Cr-Commit-Position: refs/heads/master@{#385967}
==========

[commit-bot: I haz the power, 2016-04-08 03:12:04]

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