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

Support a flag on widgets to automatically pin them to the room #15267

Closed
turt2live opened this issue Sep 23, 2020 · 14 comments · Fixed by matrix-org/matrix-react-sdk#5553
Closed

Comments

@turt2live
Copy link
Member

Widgets are useful for some interactions with bridges, bots, etc where it'd be nice to have the widget pre-pinned so the bot doesn't have to explain where to find the thing

@Cadair
Copy link

Cadair commented Sep 23, 2020

@Half-Shot and I were talking about using a widget in the slack bridge DM room to provide a nice "click this to login to slack" way of authenticating with the bridge, and the openid stuff for widgets would allow you to do this without having to send commands to the bridge bot, but the current widget UX doesn't really make it work.

@fooness
Copy link
Contributor

fooness commented Oct 11, 2020

We kinda relied on automatic widget pinning for the start of our semester on November 1st, as this feature was the default for the last months. Is there any way this feature will be (re-)implemented soon-ish? We would be very happy about this, the current state is rather non-ideal.

Thank you very much!

@t3chguy
Copy link
Member

t3chguy commented Oct 11, 2020

Shouldn't this be a spec issue?

@turt2live
Copy link
Member Author

Element made the UI decision, not the spec. Element then is in a position to solve the problem (if it wants to), which might result in a MSC down the line, however this is largely something that would be client-specific and not part of the spec.

@t3chguy
Copy link
Member

t3chguy commented Oct 11, 2020

Good point.

@t3chguy t3chguy added the X-Needs-Product More input needed from the Product team label Oct 11, 2020
@fooness
Copy link
Contributor

fooness commented Oct 18, 2020

Any news on reverting this breaking change? 😔

For digital education and teaching this feature was mandatory. We’re in the process of rolling out Matrix/Element for everyone at our university and now that this feature was removed suddenly over night … we have lots and lots of problems.

@t3chguy
Copy link
Member

t3chguy commented Oct 18, 2020

How would such a flag work with regards to the pinning limit? E.g what if a user already has two pinned widgets and an admin adds a new widget with this proposed flag, what would happen?

@turt2live
Copy link
Member Author

the same thing that happened before: pin it anyways

@t3chguy
Copy link
Member

t3chguy commented Oct 18, 2020

With our stricter sizing requirements that simply won't be possible. The resizer will fail to function with >3 pinned due to the complexity of the behavioural requirements.

@turt2live
Copy link
Member Author

then don't auto-pin past 3 and leave them unpinned? The problem statement is "I added a widget for the first time, and it's completely missing from my room". Most of the use cases for this will have no more than 1 widget they need to worry about.

Quite frankly, it's extremely irritating that custom widgets don't auto-pin as it prevents the vast majority of use cases for widgets from functioning. Can we please just make m.custom auto-pin?

@t3chguy
Copy link
Member

t3chguy commented Oct 18, 2020

I believe design wants auto-pinning gone altogether so unlikely

@turt2live
Copy link
Member Author

turt2live commented Oct 18, 2020

That'll get added to the reasons why I can't recommend Element to people, then.

@fooness
Copy link
Contributor

fooness commented Nov 18, 2020

Any news on this topic? We’re having an extremely hard time organizing classes in our channels since widgets are treated differently for each and every user. Removing this functionality unfortunately introduced massive problems for our university.

It’s simply bad design to e.g. add a widget like Etherpad or BigBlueButton and then tell everyone (how) to access the widget. In case of audio/video conversation widgets it’s even more problematic. If you’re e.g. in a BigBlueButton call in the sidebar and then click the back button to access some other widget, you basically leave the meeting.

We’re having an extremely difficult time with this new implementation and some people already talk about not using Matrix/Element anymore for teaching due to this.

@lampholder
Copy link
Member

I just wanted to add - this is under active consideration, and the need for auto-pinning is certainly understood (particularly for the education use case).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants