Issue metadata
Sign in to add a comment
|
Unclickable notifications and "This site has been updated in the background" notifications when delivering on multiple origins at once with Win 10 native
Reported by
mtpus...@gmail.com,
Sep 28
|
||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/71.0.3562.0 Safari/537.36 Steps to reproduce the problem: This can be reproduced by sending a notifications on multiple origins at one time. One way to test this would be to use this demo site, which has been modified to serve on ports 8080:8089 and deliver to all subscribed origins. 1. Clone https://github.com/mtaylor22/simple-push-demo (forked from https://github.com/gauntface/simple-push-demo) 2. npm i 3. npm i -g gulp 4. gulp dev 5. Subscribe to localhost:8080 - localhost:8089 6. Click to send a push via XHR What is the expected behavior? All notifications are delivered normally and fire the click event handler in the service worker What went wrong? Some notifications are delivered with an additional "This site has been updated in the background" notification. Some origins seem to deliver without this (these notifications are clickable). The original notification will appear as well, but is unclickable - it does not fire the service worker's click event. Did this work before? N/A Chrome version: 69.0.3497.100 Channel: stable OS Version: 10.0 Flash Version: I believe this works properly when native push is disabled - chrome://flags/#enable-native-notifications I often see this on startup when many notifications are delivered at once
,
Oct 16
,
Nov 15
,
Nov 20
Tried testing the issue on chrome reported version# 69.0.3497.100 using Windows-10 with steps mentioned below: 1) Downloaded and extracted the zip file from URL: https://github.com/mtaylor22/simple-push-demo 2) Opened Command Prompt and executed 'npm i', 'npm i -g gulp' and 'gulp dev', after running 'gulp dev' seen "No gulpfile found" 3) Proceed with the next step by setting up local server with 8000 port, but able to see the files present in that folder @Reporter: Please find the attached screencst for your reference and let us know if we missed anything in reproducing the issue, if possible could you please provide screencst of the issue which help in better understanding and further triaging it in better way. Thanks!
,
Nov 22
Thank you very much for reviewing. I think I omitted an important step - navigating to the simple-push-demo folder before running the npm i command. I added a screencast here with more information. https://drive.google.com/file/d/1DKfBnlEUaWNR7zS7tpHX--1fSKqI8imr/view?usp=sharing
,
Jan 7
Hi Reviewer, just wanted to follow up and see if you were able to reproduce this bug. Thanks!
,
Jan 7
Thank you for providing more feedback. Adding the requester to the cc list. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by phanindra.mandapaka@chromium.org
, Sep 30