RE: DOM Parsing and Serialization action-2045

From: Fred Esch [mailto:fesch@us.ibm.com] 
Sent: 20 May 2016 18:39



“You can put DOM Parsing and Serialization
<https://www.w3.org/TR/DOM-Parsing/>  on the agenda or wait until Leone has
reviewed it. In any case, I think this doc has the same issue Rich raised
about the other parsing doc. As far as I can tell, the insertAdjacentHTML
method in section 7.2 <https://www.w3.org/TR/DOM-Parsing/#methods-2>  may be
the way CSS injects content into the DOM and that info does not get into the
accessibility tree. I suggest Joanie or a browser vendor be asked about
whether this method injects content into the DOM that does not get in the
accessibility tree.”

 

CSS generated content doesn’t affect the DOM. This from the CSS spec [1]: 

 

"Generated content does not alter the document tree. In particular, it is
not fed back to the document language processor (e.g., for reparsing)."

 

I’ve asked Travis Leithead (one of the DOM Parsing editors) for
confirmation, but suspect we should be talking to the CSS WG about how
generated content is handled in the browsers.

 

Léonie.

[1] https://www.w3.org/TR/CSS2/generate.html#propdef-content 

 

-- 

@LeonieWatson tink.uk Carpe diem