Note that there are some explanatory texts on larger screens.

plurals
  1. POFirefox support for alignment-baseline property?
    text
    copied!<p>Does Firefox have any support at all for the <a href="https://developer.mozilla.org/en-US/docs/Web/SVG/Attribute/alignment-baseline"><code>alignment-baseline</code> property</a>? When I inspect (using Firebug) SVG elements for which the <code>alignment-baseline</code> property has been explicitly set, Firebug does not list this property at all (IOW it treats is as noise). No matter what value I assign to this property, the appearance of the displayed text never changes, further suggesting that FF ignores this property altogether.</p> <p>(One other sign that FF's support for this property may be busted is that the link given in the page cited above for the CSS documentation for this property is <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/alignment-baseline">dead-as-a-doornail</a>.)</p> <p>Assuming that, as it appears, FF does not support the <code>alignment-baseline</code> property, what is the value of this property that would most closely replicate FF's default behavior?</p> <p>EDIT: For example, view this <a href="http://jsfiddle.net/APWE3/3/">jsFiddle</a> with both Chrome and FF; each line of displayed text displayed a highlighted word that has been produced with code of the following form:</p> <pre><code>&lt;tspan style="alignment-baseline:alphabetic"&gt;alphabetic&lt;/tspan&gt; </code></pre> <p>Note that all the lines look the same in FF, but not so in Chrome.</p> <p>There are a few possible candidate values for this property to replicate FF's default behavior (namely, <code>auto</code>, <code>alphabetic</code>, <code>mathematic</code>, and <code>inherit</code>); unfortunately, this experiment cannot decide the matter, and it's not clear to me which of the possible options would match FF's default behavior in the greatest fraction of cases.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload