From a82890615d02d00a6349b4138facf2f824867270 Mon Sep 17 00:00:00 2001 From: Huseyin Kaya Date: Mon, 23 Sep 2024 17:36:31 +0300 Subject: [PATCH] docs: elaborate PNG/SVG clash of favicons (#796) --- .../advanced/content/15-reference/41-asset-files.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/solara/website/pages/documentation/advanced/content/15-reference/41-asset-files.md b/solara/website/pages/documentation/advanced/content/15-reference/41-asset-files.md index ca165f3cd..8f6ad6fa7 100644 --- a/solara/website/pages/documentation/advanced/content/15-reference/41-asset-files.md +++ b/solara/website/pages/documentation/advanced/content/15-reference/41-asset-files.md @@ -6,7 +6,7 @@ description: Solara looks for overrides of certain style and asset files in the Asset files are special files with are loaded by Solara-server and thus have a special meaning, and come with defaults. Current supported assets files are: - * `favicon.png` - Image shown by the browser (usually in the tab). + * `favicon.png` and/or `favicon.svg` - Image shown by the browser (usually in the tab). If SVG is not provided, default `favicon.svg` of the solara server may override your custom favicon.png depending on the browser. Providing both PNG and SVG versions is recommended. * `style.css` - Default `CSS` used by Solara. * `custom.css` - Custom `CSS` you can override for your project (empty `CSS` file by default). * `custom.js` - Custom Javascript you can use for your project (empty Javascript file by default).