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

Bug: Custom browser setting is ignored when using a custom regex for meeting links #537

Closed
notthebee opened this issue Nov 7, 2022 · 1 comment
Assignees
Labels
bug Something isn't working

Comments

@notthebee
Copy link

notthebee commented Nov 7, 2022

App version
4.2.1

Installation source

  • AppStore

Calendars provider (selected in app)

  • macOS Calendar

Describe the bug

My default browser is set to Safari, but I would like to open my meetings in Chromium.
I've set the "Open all meeting links in..." setting to Chromium and made sure that the Chromium executable is set correctly. However, when I open a meeting from MeetingBar, it opens in Safari instead of Chromium.

I'm not sure if the issue takes place with an officially supported meeting service (e.g. Teams or Google Meet)

To Reproduce

Steps to reproduce the behavior:

  1. Create a custom Regex for meeting links2.
  2. Set the "Open all meetings in..." setting to "Chromium"
  3. Click on the menu bar icon and then click on "Join current event meeting"

Expected behavior

The meeting opens in Chromium

Screenshots

N/A

Desktop (please complete the following information):

  • macOS version: 12.15.1

Additional context

None

@notthebee notthebee added the bug Something isn't working label Nov 7, 2022
@notthebee notthebee changed the title Bug: Custom browser settings is ignored when using a custom regex meeting links Bug: Custom browser setting is ignored when using a custom regex meeting links Nov 7, 2022
@notthebee notthebee changed the title Bug: Custom browser setting is ignored when using a custom regex meeting links Bug: Custom browser setting is ignored when using a custom regex for meeting links Nov 7, 2022
@leits leits closed this as completed in a0a5a31 Mar 10, 2023
@leits
Copy link
Owner

leits commented Mar 10, 2023

Thanks, @notthebee !

Included a fix for this bug in the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants