Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Toast duration options odd behavior #203

Open
WildGenius opened this issue Dec 21, 2016 · 1 comment
Open

Toast duration options odd behavior #203

WildGenius opened this issue Dec 21, 2016 · 1 comment

Comments

@WildGenius
Copy link

General information

  • Chrome version: 55.0.2883.87 m (64-bit)
  • Prime Player version: 4.2.2
  • operating system: Win10 64-bit
  • country where you are using Prime Player: n/a
  • labs enabled in Google Music (if any): none

Description

Hide toast after seconds option only has 2 choices - 7 and 25, and, more importantly, doesn't seem to do anything. Toast duration in seconds has a proper entry field and works fine. Redundancy or bug?

Did it work before (Yes, No, I don't know):
I don't know.

Steps to reproduce

  1. Open up the extension options, turn on toasts
  2. Trigger a toast
  3. Profit

Expected behavior

See description.

Actual behavior

See description.

@svenackermann
Copy link
Owner

Hi, there have been some changes in how Chrome handles notifications. Maybe that's the reason for some weird behavior. I do not have any time at the moment to fix anything and unfortunately I'm still alone in this project.
The difference between "hide toast after" and "toast duration" is that the former one only sets the "priority" of the toast. In former Chrome versions that meant that the toast will be moved to the notification center (which does not exist anymore) after 7 or 25 seconds (see also hint description next to the option). The latter one lets Prime Player really remove the notification window after x seconds.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants