feat: Show profile banners in web UI #2207

Merged
Jade merged 2 commits from ginger/web-ui-profile-banners into main 2026-09-11 14:14:40 +00:00
Owner

This pull request shows users' MSC4427 profile banners as part of the "user card" element in the account management panel.

Pull request checklist:

  • This pull request targets the main branch, and the branch is named something other than
    main.
  • I have written an appropriate pull request title and my description is clear.
  • I understand I am responsible for the contents of this pull request.
  • I have followed the contributing guidelines:
<!-- In order to help reviewers know what your pull request does at a glance, you should ensure that 1. Your PR title is a short, single sentence describing what you changed 2. You have described in more detail what you have changed, why you have changed it, what the intended effect is, and why you think this will be beneficial to the project. If you have made any potentially strange/questionable design choices, but didn't feel they'd benefit from code comments, please don't mention them here - after opening your pull request, go to "files changed", and click on the "+" symbol in the line number gutter, and attach comments to the lines that you think would benefit from some clarification. --> This pull request shows users' MSC4427 profile banners as part of the "user card" element in the account management panel. <!-- Example: This pull request allows us to warp through time and space ten times faster than before by double-inverting the warp drive with hyperheated jump fluid, both making the drive faster and more efficient. This resolves the common issue where we have to wait more than 10 milliseconds to engage, use, and disengage the warp drive when travelling between galaxies. --> <!-- Closes: #... --> <!-- Fixes: #... --> <!-- Uncomment the above line(s) if your pull request fixes an issue or closes another pull request by superseding it. Replace `#...` with the issue/pr number, such as `#123`. --> **Pull request checklist:** <!-- You need to complete these before your PR can be considered. If you aren't sure about some, feel free to ask for clarification in #dev:continuwuity.org. --> - [x] This pull request targets the `main` branch, and the branch is named something other than `main`. - [x] I have written an appropriate pull request title and my description is clear. - [x] I understand I am responsible for the contents of this pull request. - I have followed the [contributing guidelines][c1]: - [x] My contribution follows the [code style][c2], if applicable. - [x] I ran [pre-commit checks][c1pc] before opening/drafting this pull request. - [x] I have [tested my contribution][c1t] (or proof-read it for documentation-only changes) myself, if applicable. This includes ensuring code compiles. - [x] My commit messages follow the [commit message format][c1cm] and are descriptive. <!-- Notes on these requirements: - While not required, we encourage you to sign your commits with GPG or SSH to attest the authenticity of your changes. - While we allow LLM-assisted contributions, we do not appreciate contributions that are low quality, which is typical of machine-generated contributions that have not had a lot of love and care from a human. Please do not open a PR if all you have done is asked ChatGPT to tidy up the codebase with a +-100,000 diff. - In the case of code style violations, reviewers may leave review comments/change requests indicating what the ideal change would look like. For example, a reviewer may suggest you lower a log level, or use `match` instead of `if/else` etc. - In the case of code style violations, pre-commit check failures, minor things like typos/spelling errors, and in some cases commit format violations, reviewers may modify your branch directly, typically by making changes and adding a commit. Particularly in the latter case, a reviewer may rebase your commits to squash "spammy" ones (like "fix", "fix", "actually fix"), and reword commit messages that don't satisfy the format. - Pull requests MUST pass the `Checks` CI workflows to be capable of being merged. This can only be bypassed in exceptional circumstances. If your CI flakes, let us know in matrix:r/dev:continuwuity.org. - Pull requests have to be based on the latest `main` commit before being merged. If the main branch changes while you're making your changes, you should make sure you rebase on main before opening a PR. Your branch will be rebased on main before it is merged if it has fallen behind. - We typically only do fast-forward merges, so your entire commit log will be included. Once in main, it's difficult to get out cleanly, so put on your best dress, smile for the cameras! --> [c1]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md [c2]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/docs/development/code_style.mdx [c1pc]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#pre-commit-checks [c1t]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#running-tests-locally [c1cm]: https://forgejo.ellis.link/continuwuation/continuwuity/src/branch/main/CONTRIBUTING.md#commit-messages
Owner

CI is failing by the way

CI is failing by the way
ginger force-pushed ginger/web-ui-profile-banners from c942cad843
Some checks failed
Auto Labeler / Apply labels based on changed files (pull_request_target) Successful in 3s
Checks / Prek / Check changed files (pull_request) Successful in 5s
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 9s
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m2s
Checks / Prek / Pre-commit & Formatting (pull_request) Failing after 1m14s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 8m11s
to 06780396c4
All checks were successful
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 16s
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m26s
Checks / Prek / Check changed files (pull_request) Successful in 6s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m36s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 9m19s
2026-09-01 16:56:54 +00:00
Compare
ginger force-pushed ginger/web-ui-profile-banners from 06780396c4
All checks were successful
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 16s
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m26s
Checks / Prek / Check changed files (pull_request) Successful in 6s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m36s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 9m19s
to d498853d75
All checks were successful
Checks / Prek / Check changed files (pull_request) Successful in 6s
Checks / Changelog / Check changelog is added (pull_request_target) Successful in 9s
Documentation / Build and Deploy Documentation (pull_request) Successful in 1m12s
Checks / Prek / Pre-commit & Formatting (pull_request) Successful in 1m16s
Update flake hashes / update-flake-hashes (pull_request) Successful in 1m22s
Checks / Prek / Clippy and Cargo Tests (pull_request) Successful in 9m35s
2026-09-08 16:24:10 +00:00
Compare
Contributor

look mom it's me I'm on TV in a continuwuity PR

look mom it's me I'm ~~on TV~~ in a continuwuity PR
@ -116,3 +95,4 @@
impl HtmlSafe for UserCard {}
impl UserCard {
const BANNER_KEY: &str = "chat.commet.profile_banner";
Contributor

I wonder if it'd make sense to add a fallback to the proposed stable key?

that way whenever the time comes for the MSC to be merged this won't need to be updated, though at the same time it might send the wrong message to "just write it to the stable key"

I wonder if it'd make sense to add a fallback to the proposed stable key? that way whenever the time comes for the MSC to be merged this won't need to be updated, though at the same time it might send the wrong message to "just write it to the stable key"
Owner

That's not how the unstable process works

That's not how the unstable process works
Jade approved these changes 2026-09-10 20:00:20 +00:00
@ -65,0 +65,4 @@
// it's necessary to set CSS variables using the `style` attribute without
// JavaScript. Come back to this once there's a less shitty solution.
"default-src 'none'; style-src 'self' 'unsafe-inline'; img-src 'self' https: data:; \
script-src 'nonce-{csp_nonce}'; child-src {child_src};"
Owner

The solution in this situation could be setting the variable in an inline style block with the nonce set, given it's only one global variable.

The solution in this situation could be setting the variable in an inline style block with the nonce set, given it's only one global variable.
Jade merged commit 644d247007 into main 2026-09-11 14:14:40 +00:00
Jade deleted branch ginger/web-ui-profile-banners 2026-09-11 14:14:40 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No assignees
5 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
continuwuation/continuwuity!2207
No description provided.