Skip to content

Conversation

@richvdh
Copy link
Member

@richvdh richvdh commented Jan 8, 2026

If we received the keys for a given message from another user, indicate that in the timeline, rather than just saying "authenticity not guaranteed".

Screenshot:

image

As part of this, I've factored E2ePadlock out to its own file.

Builds on functionality added in matrix-org/matrix-js-sdk#5128.

Part of element-hq/element-meta#2877

If we received the keys for a given message from another user, indicate that in
the timeline, rather than just saying "authenticity not guaranteed"
* A small icon with tooltip, used in the left margin of an {@link EventTile}, which indicates a problem
* with an encrypted event.
*/
export function E2ePadlock(props: IE2ePadlockProps): ReactNode {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A reason to not put this component in shared component as a simple component (without MVVM)?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the advantage to making it a shared component? (Shared with what?) Seems like it's more stuff that I need to change.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

To be able to use it in Aurora or in a EW modules. The advantage is to be able to use storybook on it and to benefit the story screenshot tests too

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I had a go at this, but couldn't figure out how to rebuild the shared components. Documentation seems a little lacking about how to build and maintain the shared components, making it hard for contributors outside the core Web team to get started here.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I added documentation to the shared components. Can you give it a second chance?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, done. PTAL.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

OK, done. PTAL.

... and reverted, due to the problems with tabIndex, discussed in another thread.

@richvdh richvdh requested a review from t3chguy January 15, 2026 14:51
@richvdh richvdh enabled auto-merge January 16, 2026 16:39
@richvdh richvdh added this pull request to the merge queue Jan 16, 2026
github-merge-queue bot pushed a commit that referenced this pull request Jan 16, 2026
* Factor out E2ePadlock to its own file

* Show "Bob shared this message" on messages shared via MSC4268

If we received the keys for a given message from another user, indicate that in
the timeline, rather than just saying "authenticity not guaranteed"

* Apply suggestions from code review

Co-authored-by: Florian Duros <[email protected]>

* Address review comments

* Move E2ePadlock to shared-components

* update snapshots

* Revert "update snapshots"

This reverts commit 751e31f.

* Revert "Move E2ePadlock to shared-components"

This reverts commit 172ef9f.

---------

Co-authored-by: Florian Duros <[email protected]>
@github-merge-queue github-merge-queue bot removed this pull request from the merge queue due to failed status checks Jan 16, 2026
@richvdh
Copy link
Member Author

richvdh commented Jan 16, 2026

error Error: https://registry.yarnpkg.com/@types/supercluster/-/supercluster-7.1.3.tgz: Request failed "500 Internal Server Error"

😬

@richvdh richvdh added this pull request to the merge queue Jan 16, 2026
Merged via the queue into develop with commit 92a6db5 Jan 16, 2026
37 checks passed
@richvdh richvdh deleted the rav/message_shared_info branch January 16, 2026 17:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants