diff options
| author | peter <peter@chromium.org> | 2015-04-15 13:44:28 -0700 |
|---|---|---|
| committer | Commit bot <commit-bot@chromium.org> | 2015-04-15 20:44:44 +0000 |
| commit | 539f51d6af62097059c34b1c19dfbc4352413ad7 (patch) | |
| tree | 6fdc003d363f0d38dfa6e6093d2a9e72b983d417 /tools/run-bisect-perf-regression.py | |
| parent | 3ec02d642465872d9ab7d7db600d0480a57b3cab (diff) | |
| download | chromium_src-539f51d6af62097059c34b1c19dfbc4352413ad7.zip chromium_src-539f51d6af62097059c34b1c19dfbc4352413ad7.tar.gz chromium_src-539f51d6af62097059c34b1c19dfbc4352413ad7.tar.bz2 | |
Implement Notification.data for persistent notifications.
This patch implements the Notification.data property for persistent
notifications, where the data is stored in the Notification Database.
The data associated with non-persistent notifications will never leave
Blink, so no changes are required in Chromium to support this.
As an implementation-defined limit, the size of the data will be
limited to a maximum of 1024^2 characters, with a UMA histogram tracking
the size of what developers are trying to store. The limit can then be
adjusted in future releases to match this more accurately, or as an
argument to introduce such a limit in the specification.
Further layout tests are being introduced in the following CL:
https://codereview.chromium.org/1052693002
BUG=442129
Review URL: https://codereview.chromium.org/1052683002
Cr-Commit-Position: refs/heads/master@{#325295}
Diffstat (limited to 'tools/run-bisect-perf-regression.py')
0 files changed, 0 insertions, 0 deletions