This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 17764 - Inconsistency between computed value of 'letter-spacing' and 'word-spacing'
Summary: Inconsistency between computed value of 'letter-spacing' and 'word-spacing'
Status: NEW
Alias: None
Product: CSS
Classification: Unclassified
Component: CSS Level 2 (show other bugs)
Version: unspecified
Hardware: All Windows 3.1
: P2 normal
Target Milestone: ---
Assignee: Bert Bos
QA Contact: public-css-bugzilla
URL: http://www.w3.org/TR/CSS2/text.html#s...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-12 21:04 UTC by Glenn Adams
Modified: 2012-12-04 00:52 UTC (History)
1 user (show)

See Also:


Attachments

Description Glenn Adams 2012-07-12 21:04:18 UTC
In CSS2.1 [1], the computed value of letter-spacing is specified to be:

Computed value: 'normal' or absolute length

In contrast, the computed value of word-spacing is specified to be:

Computed value: for 'normal' the value '0'; otherwise the absolute length

There appears to be no reason why these are different, i.e., the computed value of letter-spacing should take the same formulation as for word-spacing.

The present situation presents some uncertainty for the implementation of CSSOM getComputedStyle().letterSpacing, which, by the above, would appear to dictate returning the string 'normal' instead of '0'.

It is also possibly a problem that either of these should return '0' instead of '0px', which is more consistent with returning a resolved (used) length value.

I recommend that the language of both of these properties specify computed value as follows:

Computed value: for 'normal' the value '0px'; otherwise the absolute length

[1] http://www.w3.org/TR/CSS2/text.html#spacing-props