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

Transparent user avatars non-opaquely overlap in read receipts #26163

Closed
turt2live opened this issue Sep 13, 2023 · 3 comments
Closed

Transparent user avatars non-opaquely overlap in read receipts #26163

turt2live opened this issue Sep 13, 2023 · 3 comments
Labels
A-Avatar A-Read-Receipts O-Occasional Affects or can be seen by some users regularly or most users rarely S-Tolerable Low/no impact on users T-Defect X-Regression

Comments

@turt2live
Copy link
Member

Steps to reproduce

  1. Send a message with an opaque avatar
  2. Have a non-opaque avatar user read it
  3. Observe read receipts from a third account

Outcome

What did you expect?

The transparent avatar should cut into the opaque avatar, not bleed through. I believe this was the case at some point in the past.

What happened instead?

image

There is a subtle outline on the transparent user's avatar, and the opaque avatar is bleeding through.

Operating system

Windows 11

Application version

Element Nightly version: 0.0.1-nightly.2023091301 Olm version: 3.2.14

How did you install the app?

The Internet

Homeserver

t2l.io

Will you send logs?

No

@robintown robintown added X-Regression S-Tolerable Low/no impact on users A-Read-Receipts A-Avatar O-Occasional Affects or can be seen by some users regularly or most users rarely labels Sep 13, 2023
@germain-gg
Copy link
Contributor

germain-gg commented Sep 20, 2023

Duplicate of #26159. Closing to have one thread of conversation

@turt2live
Copy link
Member Author

That looks like a related but not duplicate issue? This issue is concerned with the few remaining places where transparency exists, while the other issue is concerned with the grey.

@germain-gg
Copy link
Contributor

Yes that is true, but whatever we settle on will apply to both issues. I've also commented on the counterpart to explain that we have to take in consideration the issue here.
I'm not overly inclined to keep the two open as this will split the discussion needlessly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-Avatar A-Read-Receipts O-Occasional Affects or can be seen by some users regularly or most users rarely S-Tolerable Low/no impact on users T-Defect X-Regression
Projects
None yet
Development

No branches or pull requests

3 participants