Urgent.News

What's breaking now, across thousands of outlets.

Tech

Why Confluence Cloud turns your SVG into a flat image

Short answer. An SVG file is not only a picture: it can carry links, scripts and references to outside resources. Rendering one live inside a page would let an attachment run code on your site, so Confluence Cloud converts it to a raster image before it is displayed. The picture survives. Everything interactive inside it does not, and there is no administrator setting that turns this behaviour…

SVG files in Confluence Cloud are converted to flat images before display to prevent potential security risks. This is because SVGs can contain links, scripts, and references to external resources, which could allow an attacker to execute malicious code on a site if rendered inline. Confluence Cloud stores the original SVG attachment, so it remains unchanged and downloadable, but the rendered version is a rasterized image without any interactive elements.

This means hyperlinks, hover states, tooltips, scripts, animations, and selectable text are all removed from the displayed image. The image itself remains intact, but its clarity may be slightly reduced when zoomed in due to its fixed resolution. While some users might recommend using the HTML macro or custom user macros in older versions of Confluence Server, this approach does not apply to Confluence Cloud, which does not support native HTML macros.

Instead, alternatives include using diagramming apps like draw.io, which preserve links and interactive elements, or breaking down large diagrams into smaller pages. For a more secure solution, using a third-party app that parses the SVG, removes unsafe elements, and renders only the safe content is recommended. These apps ensure that dangerous content never reaches the page and can store links as references to pages, maintaining correct functionality even when pages are renamed or moved.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

Spec-Driven Development in React Native: an MVP that lists the world's earthquakes, specified before writing code

Un agente de código ya escribe una app funcional en una tarde. El problema dejó de ser producir el código y pasó a ser otro: el agente no escribe peor código sin una especificación, escribe un código…

  • Spec-Driven Development prioritizes defining software requirements before coding
  • MVP React Native app lists recent global earthquakes using Expo
  • SDD separates specification, technical plan, and tasks for maintainable development

Spec-Driven Development in React Native: an MVP that lists the world's earthquakes, specified before writing code

A coding agent can already write a working app in an afternoon. The problem is no longer producing the code; it is something else: without a specification the agent doesn't write worse code, it writes…

  • Spec-Driven Development separates specification, technical plan, and tasks
  • For React Native MVP, specification defines desired earthquake listing functionality
  • SDD artifacts are version-controlled and persist beyond agent session

i wrote down ~100 public saas pricing pages so i'd stop guessing

I kept pricing off gut instinct + one competitor for way too long. You know the move. competitor is $29 so you're $19. or you're $49 because "premium." neither is a strategy.

  • Study examined 100 public SaaS pricing pages to avoid uninformed decisions
  • Found common pricing strategies: annual discounts, free tiers, varying structures
  • Pricing models varied widely based on product, target audience, and company

More from Saturday 5 September →