feat: add custom CSS styling#1745
Conversation
|
Hi, thanks for the contribution! |
|
Hello Timon, Thank you for your contribution. We are discussing if this feature makes sense as a user feature. Adding custom CSS is always risky. This is something not guaranteed to work across upgrades, and it may break the UI. If we add it, it shouldn't be so prominent for a general user. This is not something an average user would do on the same level as switching between a light/dark color scheme. Especially if it is a text area to manually input the CSS code. At the same time, for a sysadmin manually opening the client on every machine to insert the CSS may not be the most convenient solution. Instead of storing the CSS code in the config, I'd use a CSS file. For example, a fixed In the app settings then it should be indicated that the custom CSS is applied. An alternative way would be to include the styles via |
Signed-off-by: Timon Laptop <bedynek@themarmalade.com> Co-authored-by: Cursor <cursoragent@cursor.com>
|
ty for the feedback. Maintaining a custom build is something we would like to move away from in the future, so the .overrides approach would not be ideal for us long-term. I reworked the PR to avoid exposing custom CSS as a regular user-facing setting. It now loads a fixed custom.css file from the app data location, with support for %ProgramData%\Nextcloud Talk\custom.css on Windows for managed/multi-user deployments. The settings UI only indicates when custom CSS is applied. |

Adds a local Custom CSS option to Talk Desktop settings using the existing app config storage. Changes apply immediately in the desktop renderer, and clearing the field removes the custom styling. We use custom CSS internally, for example to display ticket messages from our ticket system and for theming.