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 15190 - List of region style properties
Summary: List of region style properties
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:
URL:
Whiteboard: editorial
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-14 22:51 UTC by Vincent Hardy
Modified: 2012-10-04 22:17 UTC (History)
2 users (show)

See Also:


Attachments

Description Vincent Hardy 2011-12-14 22:51:13 UTC
implementation experience has shown that it was more practical to have a style rule for region styling and limit the number of properties that could be styled. There are questions about the precise list of properties that should be supported.

Proposal

in addition to the properties supported by ::first-line, we should support the various border properties and allow the width, padding, margin and border properties. The rationale for allowing width, margin, border and padding properties is that we already have to support variable width containers and, therefore, will have to support varying width content (e.g., a block with 'width: 50%' or 'width: 40em' that spans multiple regions of different widths).
Comment 1 Vincent Hardy 2012-02-04 09:52:25 UTC
In the following review:

http://lists.w3.org/Archives/Public/www-style/2012Feb/0001.html

Alex is suggesting:

"I think region styles should also support multicolumn properties. Channing width will already affect number of columns, so for implementation it will make very little difference."
Comment 2 Alan Stearns 2012-10-04 22:17:02 UTC
The region itself might have multicolumn properties set, but I'm not sure it makes sense to specify that elements in the region's fragment should change the number of their columns. Since the spec is up-to-date with the first comment and I'm rejecting the second comment, I'm closing out this bug.