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 16912 - Emphasize use of 'flex' instead of longhand properties in spec
Summary: Emphasize use of 'flex' instead of longhand properties in spec
Status: RESOLVED FIXED
Alias: None
Product: CSS
Classification: Unclassified
Component: Flexbox (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Tab Atkins Jr.
QA Contact: public-css-bugzilla
URL:
Whiteboard:
Keywords:
Depends on: 16145
Blocks:
  Show dependency tree / graph
 
Reported: 2012-05-02 22:41 UTC by Daniel Holbert
Modified: 2012-05-09 22:52 UTC (History)
3 users (show)

See Also:

Attachments

Description Daniel Holbert 2012-05-02 22:41:12 UTC 
Per discussion w/ fantasai & alex, we want to make sure the spec strongly emphasizes use of the 'flex' property (rather than the three sub-properties which are likely to be split out in bug 16145)

We should have examples using flex: <integer>, flex: none, and flex: auto, since authors probably want to use one of those options, in most cases.
Comment 1 Tab Atkins Jr. 2012-05-09 22:52:56 UTC 
Fixed!

(Examples are covered by bug 16913.)