57
Custom css in web widget
Axel Vermeil
It would be great to be able to customize the look and feel of the web widget! Offering specific options (for color etc) in the canny admin panel will probably never be enough, so it might be easiest to allow an optional URL to a CSS file in the canny css code, which would be injected into your iframe. You would also need to make sure you have good class names ;)
M
Madhu
Any update on this? I am using bootstrap@5.3.x with it's auto dark mode. Would be great if canny can inherit whatever theme is being used on the site which is embedding canny (at least the background and font colours)
Lisa diKaprio
For those who're waiting for the dark mode feature: so far, just applying a filter: invert(0,9); style onto #canny-iframe like Lospec did solves the issue very well 👍
Lospec
please do this so I can do my own dark theme to make the widget match my site and not look so stupid
F
Fokke Dekker
+1 on this one. Our docs have a dark theme. Canny looks fine in the light theme but absolutely horrible in dark theme.
Mike Coulbourn
This would be a very valuable addition. It would be great to change the font and colors of statuses, for example, to better fit into the theme of our web app interface.
Andrew Rasmussen
Hey Axel Vermeil, thanks for posting. Sounds like you talked with Sarah a bit about this too.
While definitely a cool idea, I'd forever be afraid that any updates to our widget would break your customizations. We'd probably have to introduce widget versioning, provide a changelog, and document our class names. This would slow us down a lot, since we're only a nimble team of two right now.
We'll definitely keep this post open and see what other people think. If there's a specific change or configuration you have in mind, I'd love to know what it is.
Baffour Atuah
Andrew Rasmussen: I'd be grateful if there was a ways to add custom css, basically what you did here, which seems to have been removed: https://feedback.canny.io/feature-requests/p/custom-css-for-community-widget
Would be useful if it was an advanced feature with a clear warning that any updates would break customisation. So you wouldn't need you to officially support it as a public endpoint with versioning documentation etc.
Personally would like this for some minor ie11 patches, as I can see the issue and how to fix it, but you guys have dropped support!
Lospec
Andrew Rasmussen: I'm perfectly fine with it maybe breaking at some point, that's just something you accept with custom CSS.
It would still look far less broken than a giant white square embedded on my black website.
Please do it, even if you have a giant warning that it is an expert only feature that could break at any second, we would still be very grateful to have it.