W3C home > Mailing lists > Public > public-aria@w3.org > January 2016

Re: aria-ACTION-2007: Rewrite proposal to take into account that an img with source svg has no children and also to address the required owned elements

From: James Craig <jcraig@apple.com>
Date: Thu, 21 Jan 2016 18:42:16 -0800
Cc: Richard Schwerdtfeger <schwer@us.ibm.com>, Accessible Rich Internet Applications Working Group <public-aria@w3.org>
Message-Id: <150C3696-F118-44A7-81E6-C13DD835C19B@apple.com>
To: Joseph Scheuhammer <clown@alum.mit.edu>

> On Jan 21, 2016, at 1:47 PM, Joseph Scheuhammer <clown@alum.mit.edu> wrote:
> 
>> An image with external src SVG does have children. If your browser does not support them, that should be filed as a browser bug. See correct behavior in Safari/WebKit.
> 
> There may be confusion here about what "children" means here. During the meeting, Fred said that an <img src="svg"> does not produce DOM children of the <img> element.
> 
> To confirm, I tried the following with FF, Safari, and Chrome. and their respective DOM inspector tools. There is an <img> element in the DOM for each of the svg palm trees, but those <img> elements do not have DOM children.

That's just a lacking feature in the dev tools. Here's the WebKit Inspector enhancement request.
https://bugs.webkit.org/show_bug.cgi?id=121319

> http://tecfa.unige.ch/guides/svg/ex/html5/inkscape-import/html5-import-with-img.html
> 
> Also, the HTML spec for the <img> elements states that it has an empty content model [1], making <img> a leaf node.
> 
> [1] https://www.w3.org/html/wg/drafts/html/master/semantics.html#the-img-element

I believe the HTML spec should be updated to call some images a "nested browsing context" like an iframe.

> -- 
> ;;;;joseph.
> 
> 'Array(16).join("wat" - 1) + " Batman!"'
>           - G. Bernhardt -
> 
Received on Friday, 22 January 2016 02:42:47 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:58:17 UTC