- From: Chris Lilley <chris@w3.org>
- Date: Mon, 19 Mar 2012 18:54:32 +0100
- To: "Tab Atkins Jr." <jackalmage@gmail.com>
- CC: Sergey Ilinsky <sergey@ilinsky.com>, Doug Schepers <schepers@w3.org>, Cameron McCormack <cam@mcc.id.au>, SVG public list <www-svg@w3.org>
On Friday, March 16, 2012, 7:42:03 PM, Tab wrote: TAJ> On Fri, Mar 16, 2012 at 11:38 AM, Sergey Ilinsky <sergey@ilinsky.com> wrote: >> Isn't there a fundamental difference between XML "xml:space" attribute and >> CSS "white-space" property: the former instructs DOM implementation to >> preserve or not white space characters in the "Content Tree" while the later >> suggests rendering engine to create or not boxes for white space characters >> in the "Render Tree" (in browser terms)? >> Given the two mechanisms serve unrelated purposes, neither can be >> deprecated, removed or merged. TAJ> The DOM doesn't throw away white-space at all. That sort of thing TAJ> happens solely at the display (CSS) level. Both comments are correct. Sergey is correct that xml:space works at the DOM level. The two options are, effectively "do not throw away space" and "undefined (in practice, do not throw away space)". So Tab is also correct that implementations do not throw away space characters. -- Chris Lilley Technical Director, Interaction Domain W3C Graphics Activity Lead, Fonts Activity Lead Co-Chair, W3C Hypertext CG Member, CSS, WebFonts, SVG Working Groups
Received on Monday, 19 March 2012 17:54:36 UTC