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 16383 - Strictly disallow pseudo-elements to flow into regions directly.
Summary: Strictly disallow pseudo-elements to flow into regions directly.
Status: RESOLVED FIXED
Alias: None
Product: CSS
Classification: Unclassified
Component: Regions (show other bugs)
Version: unspecified
Hardware: PC All
: P2 normal
Target Milestone: ---
Assignee: Vincent Hardy
QA Contact: public-css-bugzilla
URL:
Whiteboard: cssom
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-15 00:34 UTC by Vincent Hardy
Modified: 2012-04-11 19:01 UTC (History)
3 users (show)

See Also:


Attachments

Description Vincent Hardy 2012-03-15 00:34:55 UTC
The specification is currently lose about whether or not pseudo-elements can have the flow-into property:

===
The ‘flow-into’ property does not apply to the ::first-line and ::first-letter pseudo-elements.

The effect of ‘flow-into’ on generated content such as ::marker, ::before and ::after is undefined. This may change depending on implementation feedback.
===

It seems it would be better to disallow flow-into on pseudo-elements because a) it can break the model of some pseudo elements (e.g., ::before would no longer be 'before' its element's content if moved to a flow) and b) it causes issues with the object model's NamedFlow.getContentNodes() which assumes that all that can be flown into a region is a Node (and there is no Node API to pseudo-elements).

The recommendation is to strictly disallow flow-into on all pseudo-elements.
Comment 1 Vincent Hardy 2012-03-27 21:05:16 UTC
https://dvcs.w3.org/hg/csswg/rev/511661d8b7e4