Renaming yourself in a group chat works again
- fixed Changing your display name in a conference chat failed with a network error on the deployed app: the server's cross-origin rules didn't allow the kind of request the editor sends. It worked in local development (which is same-origin and skips that check entirely), which is why it slipped through. The request now clears, and the new name reaches your other tabs and the people in the chat.
Every chat has a display name for you: what the sender sees above your messages. In group (conference) chats you can change it per conversation, so "Alice from the podcast link" and just "Alice" can coexist.
That editor sends a small update to the server when you press save. The deployed app runs on two origins (the chat interface and the API behind it), and browsers make such split-origin requests pass a safety check first: the server has to say, in advance, which kinds of requests it accepts. The list included the usual kinds but was missing the one this editor uses, so the browser stopped the save before it ever left the page. You would see "Could not save display name" and a cross-origin error in the console.
Local development never caught it because in dev the interface and the API share one origin, and that safety check is skipped entirely for same-origin requests. The list now includes the editor's request type, and a regression test pins every request type the interface sends against the list, so a future gap fails in CI instead of in front of you.
Renaming still works the same way: open the chat, click Edit next to your name in the header, type, press Enter. The change reaches your other tabs and the participants' views within a second.
← All changes