In Piwigo 13 we implemented SVG support, but we still use raw SVG in gallery and administration pages which can cause some latency if the uploaded SVGs are too big. As SVGs are mostly used for Icons and drawings with not a lot of details, this should not be felt by the users but for the worst case scenarios we will add a size limit for SVGs.
If the SVG is too big we will create a representative for it so the page loading time is shortened. We still have to decide what the limit is.
In Piwigo 13 we implemented SVG support, but we still use raw SVG in gallery and administration pages which can cause some latency if the uploaded SVGs are too big. As SVGs are mostly used for Icons and drawings with not a lot of details, this should not be felt by the users but for the worst case scenarios we will add a size limit for SVGs.
If the SVG is too big we will create a representative for it so the page loading time is shortened. We still have to decide what the limit is.
<!-- github-sync-id:1261639915 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
In Piwigo 13 we implemented SVG support, but we still use raw SVG in gallery and administration pages which can cause some latency if the uploaded SVGs are too big. As SVGs are mostly used for Icons and drawings with not a lot of details, this should not be felt by the users but for the worst case scenarios we will add a size limit for SVGs.
If the SVG is too big we will create a representative for it so the page loading time is shortened. We still have to decide what the limit is.