W3C home > Mailing lists > Public > www-svg@w3.org > October 2015

Re: IE11 and xml:space="preserve"

From: Dirk Schulze <dschulze@adobe.com>
Date: Fri, 2 Oct 2015 04:10:39 +0000
To: "Smailus, Thomas O" <Thomas.O.Smailus@boeing.com>
CC: "www-svg@w3.org" <www-svg@w3.org>
Message-ID: <D7014FC7-9D95-4216-B7B9-6E54F9E85792@adobe.com>

On Oct 1, 2015, at 1:24 PM, Smailus, Thomas O <Thomas.O.Smailus@boeing.com<mailto:Thomas.O.Smailus@boeing.com>> wrote:

I’m finding that IE11 doesn’t honor the request to preserve whitespace
OR
the getBBox() function applied to text/tspan containing extra whitespace is not computing the bounding box as expected (by giving the whitespace content contributing extent)

<tspan  font-family="arial" fill="rgb(0,0,0)"  font-size="2.02847"  >AIRSPEED - 111 TO 999 KCAS RECOMMENDED (NOT LESS THAN V     </tspan>

Contained within the <text> element is reporting/rendering as if the extra spaces after the “V” were not there or don’t contribute to the bounding box computation.

The document has xml:space="preserve" declared in the <svg > tag

xml:space is an “inheriting” attribute. The setting on any element inherits to the descendants. However, for current browsers just Firefox manages this correctly. In WebKit and Blink you need to put it on a text or tspan element as well. WebKit has a bug that I reported recently where the result just looks correct if xml:space is added to the tspans directly.

Greetings,
Dirk


As a work-around, I’m replacing all space characters with non-breaking spaces, but that, as one can imagine, makes a mess of doing text search/matching across the DOM.



Thomas Smailus

Received on Friday, 2 October 2015 04:11:10 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:55:03 UTC