- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Fri, 19 Apr 2013 14:54:34 -0700
- To: Alan Stearns <stearns@adobe.com>
- Cc: Brad Kemper <brad.kemper@gmail.com>, "www-style@w3.org" <www-style@w3.org>
On Fri, Apr 19, 2013 at 2:00 PM, Alan Stearns <stearns@adobe.com> wrote: > On 4/19/13 1:50 PM, "Brad Kemper" <brad.kemper@gmail.com> wrote: >>What happens when the author tries to flow contents from a replaced >>element like an image? > > I think it's exactly that happens when you flow contents from a > non-replaced element like a div. Remember that we're only affecting the > visual formatting. If you flow contents from a div, the boxes that would > render in the div's content box are rendered in the region chain instead. > So if you flow contents from an image, the box that would render in the > image's content box (the image itself) is rendered in the region chain. In > both cases, the stuff outside the content box (borders, etc.) remain in > the normal flow. > > I am not an expert on image elements. So if I have made any mistaken > assumptions here, please let me know. The problem is that we don't have a notion of "the image itself" yes. We skirt the edges in places, such as the object-fit/position properties, but still don't talk about it as a first-class thing that can be manipulated. This causes problems for subclassing elements in Web Components, because while some elements have a clear notion of "built-in shadow DOM", it's unclear exactly what's inside of a <img> or <video>. Probably we just need to reify the concept somehow, so that, similar to text, "replaced content" is a thing that simply ignores all CSS properties, and generally tries to fit itself to its container somehow. ~TJ
Received on Friday, 19 April 2013 21:55:21 UTC