Invalid timestamp is set for "This site has been updated in the background" notification. |
||||
Issue descriptionChrome Version: 63.0.3225.0 OS: Chrome OS What steps will reproduce the problem? (1) Enable push notification in a website. (2) Wait for notification to arrive. What is the expected result? The notification header should be "now". What happens instead? The notification header says "418y" (418 years ago)
,
Sep 26 2017
Thank you! I wrote the CL https://crrev.com/c/683914 (just pasted your fix :)
,
Sep 26 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/f1b84062d58fd80832fccfb828b2d5c25b6b7388 commit f1b84062d58fd80832fccfb828b2d5c25b6b7388 Author: Tetsui Ohkubo <tetsui@chromium.org> Date: Tue Sep 26 06:08:16 2017 Set timestamp to push messaging default notification. This CL sets current timestamp to the default notification of push messaging. Previously, invalid time was shown when new style notification chrome://flags/#enable-message-center-new-style-notification is Enabled (which is ToT default). TEST=manual BUG= 768695 Change-Id: Id253c990d39a8f8df71472c47137b8252a9186d4 Reviewed-on: https://chromium-review.googlesource.com/683914 Commit-Queue: Tetsui Ohkubo <tetsui@chromium.org> Commit-Queue: Peter Beverloo <peter@chromium.org> Reviewed-by: Peter Beverloo <peter@chromium.org> Cr-Commit-Position: refs/heads/master@{#504296} [modify] https://crrev.com/f1b84062d58fd80832fccfb828b2d5c25b6b7388/chrome/browser/push_messaging/push_messaging_notification_manager.cc
,
Sep 26 2017
,
Sep 28 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by peter@chromium.org
, Sep 26 2017