intrinsicsize conflicting with CSS object-fit

I recently added the `intrinsicsize` attribute to our news site when I was anyway working on our image component, as I liked the idea behind it and the provided layout stability helps our readers massively. Of course it was not yet active in browsers, but I wanted to be prepared for that day.

After a few weeks I switched the "Experimental Webplatform Features" flag on, as I wanted to demo new stuff in a meetup talk. Of course, I didn't turn the flag back off afterwards, so that `intrinsicsize` stayed activated.

Now, when I returned to our site, I discovered that suddenly certain images (but not all) where distorted. E.g.:


[link](https://rp-online.de/nrw/staedte/neuss/kammelle-us-koelle-2019-im-crowne-plaza-neuss-feiern-mit-brings-hoehner-und-guido-cantz_aid-35695693)


[link](https://rp-online.de/sport/fussball/fortuna/fortuna-duesseldorf-burgfrieden-zwischen-friedhelm-funkel-und-schaefer_aid-35674969)

What the distorted images had in common was that they had the CSS property `object-fit` set - either to `contain` (1. example) or to `cover` (2. example). The ``'s `width` and `height` attributes were set to the desired size of the area into which to fit the respective image. And `intrinsicsize` was being fed the exact same values. E.g.

```html

```

See this isolated [demo](https://codepen.io/Schepp/pen/WLqJqq).

At least for me this result was unexpected, as to my understanding, the job of the `intrinsicsize` attribute was to provide layout stability for when not both axis' dimensions are provided.

But why would it interfere with `object-fit`?

I know that in the explainer you write:

> the image would raster at these dimensions

and that this is why the result comes together as it does.

(Although, to be precise, it does not raster at the given dimensions, but instead it just scales the original image in both axis until it meets the given size. Otherwise [this image](https://codepen.io/Schepp/pen/OreZGa) would be pixelated, which it is not)

**My question/food for thought now is:** should this behavior still apply for when `object-fit` is active? What real world use case is there to stick with the current state of implementation?

Because the way it is now, when serving an `` element, I would need to know if some stylesheet applies the `object-fit` property and if so I would need to strip the `intrinsicsize` attribute from my HTML output. Which is not obvious to figure out from the HTML perspective.

`object-fit` should either overrule `intrinsicsize` or there should be an additional CSS property that overrides the HTML sibling, as do CSS'es `width` and `height`.