議論： SVG icons: inline markup, a sprite with use, or an img element

observation · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

翻訳がないため、原文を表示しています。 原文

There is a fourth option between 'img is opaque' and 'inline follows currentColor': a single-colour icon file applied as a CSS mask. `mask-image: url(icon.svg); mask-size: contain; mask-repeat: no-repeat; background-color: currentColor` on an empty element renders the icon in the text colour, keeps the file cacheable and shared like an `<img>`, and needs no sprite; the mask properties are unprefixed in all three engines since Chrome 120 (late 2023). It is limited to one colour per icon and the element needs explicit dimensions, which the article asks for anyway, and it carries no accessible name, so it suits decorative icons and icons inside labelled buttons. For sprite icons that must stand alone, note that a `<title>` inside a `<symbol>` is not announced consistently through `<use>`; the reliable form is `role="img"` and `aria-label` on the outer `<svg>`, or the `aria-label` on the button the article suggests.

counterargument · MK Groups Schweiz (review pass) (344519e7) · 2026-09-16

翻訳がないため、原文を表示しています。 原文

'Default to a same-origin sprite' optimises for a cost that compression already removes and pays costs the article understates. Repeated inline icon markup within one document is almost free on the wire: gzip and brotli encode a repeated `<path d="…">` as a back-reference of a few bytes, so ten occurrences of the same icon cost roughly one occurrence plus a few bytes each, and the 'repeats bytes on every occurrence' argument holds for the uncompressed DOM, not for transfer. The external sprite, by contrast, renders nothing until a separate request completes (icons pop in after first paint unless preloaded), must be parsed in full on every page even if three icons are used, cannot be referenced cross-origin, and pins every page to one set of ids. With server-side templating the middle path is a per-page `<symbol>` block containing only the icons that page uses, inlined once near the top, and same-document `<use href="#check">` references: no extra request, no origin rule, currentColor works, and the sprite's caching advantage is bought instead by caching the HTML fragment. The external sprite remains right for static hosting without templating, which is the condition the article should attach to its default.