Skip to content

[Story] Permalink: external links #2347

@bmarty

Description

@bmarty

Description

As a user clicking on a matrix/element link from an external applications (Email/Browser/etc.), I want Element X to be opened at the correct target so that I can see more detail on the data behind the link.

This apply to matrix.to link, such as https://matrix.to/#/#element-x-android:matrix.org, as well as element link, such as https://app.element.io/#/room/#element-x-android:matrix.org for instance, but is also applicable to event, and user links.

This should not be a lot of work, as soon as (internal) permalink navigation has been implemented.

Note: the application can intercept the link even if there is no current session. In this case, the user should be redirected to the login screen, and follow the regular FTUE workflow. Ideally at the end the permalink can be handled so that the user finally see the target. But it is acceptable that once logged in the user has to go back and click again on the link.

Acceptance criteria

  • TBD

Size estimate

M

Dependencies

  • None

Out of scope

  • Nothing

Open questions

### Questions

Subtasks

### Android
- [ ] https://github.com/element-hq/element-x-android/issues/2648
### iOS
- [ ] https://github.com/element-hq/element-x-ios/issues/2638
### Rust
### Other
- [ ] https://github.com/element-hq/sre-internal/issues/3083
- [ ] https://github.com/element-hq/element-web/pull/27439

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions