chrome.notifications.onClosed called with byUser true when notification simply times out
Reported by
ryanjold...@gmail.com,
Oct 3 2017
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36 Steps to reproduce the problem: 1. Show a notification using chrome.notifications.create 2. Wait for the notification to time out 3. See that chrome.notifications.onClosed listener is called with byUser true What is the expected behavior? I expect chrome.notifications.onClosed called with byUser false since no user interaction occurred What went wrong? byUser is reporting the incorrect value Did this work before? N/A Does this work in other browsers? N/A Chrome version: 61.0.3163.100 Channel: stable OS Version: 10.0 Flash Version: I have attached a dummy extension that will let you quickly repro the issue (just wait a few second and see the log line after the notification fades out)
,
Oct 4 2017
,
Oct 6 2017
ryanjoldenburg@ Thanks for the issue. Able to reproduce this issue on Windows 7,10 and Ubuntu 14.04 using the latest Stable 61.0.3163.100, but unable to reproduce this issue on the latest Canary 63.0.3233.0 and Dev 63.0.3230.0. Performed reverse bisect and below is the Bisect Information. Reverse Bisect Information: ===================== Good build: 62.0.3202.21 Bad Build : 62.0.3202.18 Note: As the good and bad builds are branch builds, cannot execute the per-revision script for finding the Suspect CL. Hence through Manual Bisect providing the Changelog URL from Omahaproxy. Change Log URL : ================== https://chromium.googlesource.com/chromium/src/+log/62.0.3202.18..62.0.3202.21?pretty=fuller&n=10000 As we are unable to find the right suspect from the above ChangeLog, requesting someone from Dev to look into the issue. Hence marking this issue as Untriaged for further update from Dev. Adding ReleaseBlock-Stable as this is a recent regression. Please feel free to remove if this is not the case. Thanks..
,
Oct 7 2017
susanjuniab@, You have to perform reverse bisect here since the bug exists only in Chrome Stable#61.0.3163.100. Here is the change log i got after the reverse bisect: https://chromium.googlesource.com/chromium/src/+log/1ec60c26b4712a1776a72f4d4cdd9b4c960c5bfd..961c74da485f407caf877fe2eadc84e767af3ebc From here, you can see the fix which has been landed. At the end it's a dupe of https://bugs.chromium.org/p/chromium/issues/detail?id=760608. Thank you! |
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by ryanjold...@gmail.com
, Oct 3 2017