"Failure to create room": When user isn't allowed to create an alias

[jaller94]

Steps to reproduce

0. Have a home sever that restricts who can create an alias.
   • alias_creation_rules
1. Create a public room with an alias.

Outcome

What did you expect?

• Ideally, the room creation dialog would know that I cannot create an alias.
• As a fallback, an error should tell me that I cannot create public rooms with an alias.

What happened instead?

Application version

Element version: 1.11.19 Olm version: 3.2.12

Homeserver

Fairly recent Synapse

Will you send logs?

Yes

[jaller94]

This prevents me from creating a public room in the dialog, because an alias is required.

Workaround:

• Create a private room
• Make it public through the room settings

[jaller94]

Also, the following error is thrown:

Uncaught TypeError: can't access property "message", e is undefined
showJoinRoomError RoomViewStore.tsx:579
joinRoomError RoomViewStore.tsx:616
onDispatch RoomViewStore.tsx:300

[t3chguy]

The Matrix Spec doesn't have provisions for whether a user can or cannot assign aliases, it implies everyone can, therefore the server here is slightly out of spec IMO.

[gaelledel]

Client needs to query whether it can create aliases in advance of creating a room. This requires spec work.

[gaelledel]

When engineering comes to this piece of work, we can re add the X needs design label to collaborate on copy