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

custom widgets need to support custom names to differentiate them from each other #1270

Open
ara4n opened this issue Nov 19, 2017 · 8 comments

Comments

@ara4n
Copy link
Member

ara4n commented Nov 19, 2017

especially on Android, where they all get labelled precisely the same thing, so you don't know which you're selecting

@lampholder lampholder added the P2 label Nov 23, 2017
@stephanerosa
Copy link

stephanerosa commented Oct 21, 2020

Yes, that would be a very nice quick fix because it does really not make any sense from a UX prospective. Can I suggest the addition of a custom icon as well ?

image

@t3chguy
Copy link
Member

t3chguy commented Oct 21, 2020

This is a Scalar issue, the Widgets API lets them do that

@stephanerosa
Copy link

Actually I didn't think of changing that state myself manually. It works like a charm :-)
(Ok DeepL does not load but it was just to test the naming)

image

@t3chguy
Copy link
Member

t3chguy commented Oct 21, 2020

For the icon you can specify avatar_url with an mxc resource in the same widget event content

@stephanerosa
Copy link

That perfectly worked. Thank you !
image

@t3chguy
Copy link
Member

t3chguy commented Oct 21, 2020

Hilariously I just realised I never tested avatar_url on Widgets when I added support for it, you appear to be its first tester :D

@stephanerosa
Copy link

I confirm it working on Element-web and Element-desktop.
On Element-android the renaming works but there is no avatar in the first place so I cannot tell
I do not have an iPhone to test Avatar-ios

@t3chguy
Copy link
Member

t3chguy commented Oct 21, 2020

The MSC which adds support for avatars on Widgets is new and only Web/Desktop support it yet

@t3chguy t3chguy transferred this issue from element-hq/element-web Mar 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants