Re: [csswg-drafts] [css-link-params-1] Discussion over whether link-parameters should be inherited (#13667)

Inheriting the link parameters does have big side effects. It means the parameters are appended to _all_ external resources, which is not what I'd expect.

The spec isn't very clear about what it means by "an element representing an external resource". Besides the mentioned `<img>`s and `<iframes>` this may also include `<link>`s, `<script>`s, `<object>`, and any other external resource plus _all_ external CSS resources.

So if `link-parameters` inherited, those parameters would be appended to every single resource in the cascade, which is probably not what authors expect.

So I think it is fine to have `link-parameters` be not inherited and let authors explicitly define where they want the parameters to apply.

Even without inheriting, theming SVGs or changing logos can already be easily achieved by something like

```html
<img class="logo" src="logo.svg">
<img class="icon" src="icon.svg">
```

```css
.logo,
.icon {
  link-parameters: param(--theme, blue);
}
```

or

```html
<img class="logo" src="logo.svg#param(--theme, blue)">
<img class="icon" src="icon.svg#param(--theme, blue)">
```

or for CSS resources via

```
.logo {
  background-image: url('logo.svg') param(--theme, blue);
}

.icon {
  background-image: url('icon.svg') param(--theme, blue);
}
```

Sebastian

-- 
GitHub Notification of comment by SebastianZ
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13667#issuecomment-4110697833 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 23 March 2026 13:41:45 UTC