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.

Sign up for GitHub

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

Jump to bottom

url does not contain custom port when opening notification in browser tab #80

Open
freeflyk opened this issue May 5, 2024 · 0 comments
Open

url does not contain custom port when opening notification in browser tab #80

freeflyk opened this issue May 5, 2024 · 0 comments
Assignees
@0x50f13
Labels
bug Something isn't working investigate The issue requires investigation and currently can't be labeled as bug or feature request certainly

Comments

@freeflyk
Copy link
Contributor

freeflyk commented May 5, 2024

Hi 0x50f13. I found that when taping on the notification to open the chat in a browser tab the url that is used does not contain a custom port number. Thus, using any other port then 80 or 443 will make the browser to not open the correct page.
@0x50f13 0x50f13 added bug Something isn't working investigate The issue requires investigation and currently can't be labeled as bug or feature request certainly labels May 6, 2024
@0x50f13 0x50f13 self-assigned this May 6, 2024
@0x50f13 0x50f13 added this to the 1.1-beta20 milestone May 11, 2024
@0x50f13 0x50f13 removed this from the 1.1-beta20 milestone Jun 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@0x50f13 0x50f13

Labels
bug Something isn't working investigate The issue requires investigation and currently can't be labeled as bug or feature request certainly
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@0x50f13 @freeflyk