Bug 15457 - Computed value of 'content' property seems undefined for :first-line and :first-letter
Summary: Computed value of 'content' property seems undefined for :first-line and :fir...
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
Depends on:
Reported: 2012-01-08 19:33 UTC by Anton P
Modified: 2012-12-04 00:51 UTC (History)
0 users

See Also:


Note You need to log in before you can comment on or make changes to this bug.
Description Anton P 2012-01-08 19:33:19 UTC
Reported by Simon Sapin.

The Computed Value line of the 'content' property defined in 12.2 (http://www.w3.org/TR/CSS2/generate.html#content) says:

  # On elements, always computes to 'normal'. On :before and
  # :after, if 'normal' is specified, computes to 'none'.
  # Otherwise, for URI values, the absolute URI; for attr()
  # values, the resulting string; for other keywords, as
  # specified.

This appears to omit the cases of the :first-line and :first-letter pseudo-elements.  This is a consequence of the spec's convention of using the word "elements" to mean "elements or pseudo-elements".  However, in this instance, the effect is jarring since treating :before and :after as if they were not covered by the first sentence fools the reader into thinking that no pseudo-element is covered by that sentence.

Conversation begins: http://lists.w3.org/Archives/Public/www-style/2011Nov/0797.html

Bug description: http://lists.w3.org/Archives/Public/www-style/2011Dec/0113.html