Skip to content

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

@freeflyk

Description

@freeflyk

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.

Metadata

Metadata

Assignees

Labels

bugSomething isn't workinginvestigateThe issue requires investigation and currently can't be labeled as bug or feature request certainly

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions