First notification is not shown
Reported by
maria.hu...@gmail.com,
May 29 2017
|
||||||||||
Issue descriptionChrome Version : 58.0.3029.110 (64-bit) OS Version: Windows 10.0 URLs (if applicable) : https://developer.mozilla.org/en/docs/Web/API/notification#Example Other browsers tested: Add OK or FAIL after other browsers where you have tested this issue: Safari 5: Firefox 4.x: OK IE 7/8/9: What steps will reproduce the problem? 1. Start Chrome. If it was running already, close it and and end all Chrome processes in the task manager. Then restart. 2. Go to https://developer.mozilla.org/en/docs/Web/API/notification#Example 3. Click "Notify me", grant permission if necessary 4. Notice that there is no notification 5. Click the same button again 6. Notice that there is a notfication What is the expected result? Chrome should show the first notification What happens instead of that? Chrome does not show the first notification, but shows subsequent ones. Please provide any additional information below. Attach a screenshot if possible. The same problem can be observed here: https://jsbin.com/ziwod/2/edit?html,js,output Seems to be problem with the Notification API. After playing around with API the browser completely stopped showing notifications after some time. However, I have not reproduced that.
,
May 30 2017
Tested the issue on Windows 10 using chrome stable version #58.0.3029.110 and Latest Canary #60.0.3114.0 and Unable to repro this issue. Following are the steps followed to reproduce the issue. ------------ 1. Launched chrome 2. Navigated to https://developer.mozilla.org/en/docs/Web/API/notification#Example 3. Clicked on "Notify me" and Granted permission by clicking on 'Allow' button. 4. And able to see First notification. Attaching screen cast for reference. maria.husmann@ - Could you please verify the screen-cast and let us know if anything is missed from our side.If possible please provide an expected behavior screen cast explaining about the issue. Thanks...!!
,
May 30 2017
Thanks for looking into this. Your screencast shows the expected the behaviour. I'm at work now, using a different machine (windows 7) and I'm unable to reproduce the issue here. I'll have another look when I have access to my laptop where I had the issue. There, I did observe it both on stable and Canary.
,
May 30 2017
Thank you for providing more feedback. Adding requester "jbanavatu@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
May 30 2017
This actually seems to be a bug in the code on https://jsbin.com/ziwod/2/edit?html,js,output In short, permission is being requested on page load. If we ignore that prompt, then what happens when clicking on the button is the following: 1. Check if the Notification object exists. 2. If so, check the Notification.permission value, then either: a) when different from "granted", request permission b) if set to "granted", show the notification This means that it either requests permission *or* shows a notification, not both. As such, it's expected to have to click twice. I cannot reproduce this issue on Mozilla's page either..
,
May 30 2017
Ok, I'm back on my laptop. I've made an interesting observation. The issue only occurs when I attach an external monitor. So on the same laptop, when only using the laptop screen, it works as expected. As soon as I attach an additional external screen, the issue appears. No issue in Firefox and Edge with the same setup.
,
May 30 2017
Thank you for providing more feedback. Adding requester "peter@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 7 2017
Tested the issue on Windows 10 with dual monitor setup using chrome stable version #58.0.3029.110 and Latest Canary #60.0.3122.0 and Unable to repro this issue. Following are the steps followed to reproduce the issue. ------------ 1. Launched chrome 2. Navigated to https://developer.mozilla.org/en/docs/Web/API/notification#Example 3. Clicked on "Notify me" and Granted permission by clicking on 'Allow' button. 4. And able to see First notification. Attaching screen cast for reference. maria.husmann@ - Could you please re-try the same scenario on clean profile with no apps/extensions and let us know observations. Thanks...!!
,
Jun 7 2017
kkaluri@ I will do that and report on the exact setup. Might take a couple of days though, because I don't have access to that machine for now. I also remember that the issue only appeared with the "extend" configuration and not with "duplicate".
,
Jun 7 2017
Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 8 2017
Still waiting for an update as per C#11.
,
Jun 12 2017
Here's further info: I can replicate the bug on a clean Chrome Canary. I also notice that the bug only manifests itself when the additional screen is on the left of the original laptop screen. When I switch the screens so that the extended screen is on the right, the behaviour is as expected. Furthermore, the bug only appears if that extended screen is also set to be the main screen and the original screen has a scale factor set. So to replicate do the following: 1. Add a screen and set Windows to extend mode. 2. Make sure the additional screen is arranged to the left of the original screen 3. Set the additional screen to be the main screen. 4. Set a scale factor of 150% in the orignal screen (the right one) I've attached a file with my screen configuration.
,
Jun 12 2017
Thank you for providing more feedback. Adding requester "ajha@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Jun 12 2018
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||||||||||
►
Sign in to add a comment |
||||||||||
Comment 1 by nyerramilli@chromium.org
, May 30 2017