Skip to content

feat: separate browser notification from ping sound in plugin settings #69

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

Open
wants to merge 6 commits into
base: v0.0.x
Choose a base branch
from

Conversation

GuiLeme
Copy link
Collaborator

@GuiLeme GuiLeme commented Aug 15, 2025

What does this PR do?

This PR separates the previous pingSoundEnabled which controlled the browser notification as well into the 2 settings:

  • pingSoundEnabled: Same name, different feature - It controls only the ping sound;
  • browserNotificationEnabled: Now, this flag controls the browser notification;

One other important change is: the ping sound comes enabled by default while the browser notification doesn't.

Motivation

For the browser notification to appear, it needs to ask for permission from the browser, which is not the ideal for every user - it can cause the person to question their privacy while using BBB. Despite that inconvenience, it's good to maintain the ping sound.

A good solution, then, is to separate the flag to enable the ping sound from the flag to enable the browser notification.

More

This PR depends on the recent refactor from #68.

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

Successfully merging this pull request may close these issues.

1 participant