Tweak and format HISTORY.md changes for the NEXT release, 0.3.0

This commit is contained in:
Eric Ferraiuolo 2013-09-04 13:06:25 -04:00
parent 6a36aecd6b
commit d1fb3d4233

View File

@ -4,8 +4,8 @@ Pure Change History
NEXT
----
* (!) Pure now requires the Base module (which is Normalize.css) to be on the
page. Pure has essentially always required the styles provided by
* __[!]__ Pure now requires the Base module (which is Normalize.css) to be on
the page. Pure has essentially always required the styles provided by
Normalize.css via the Base module, and this now makes it a firm requirement.
The `pure-min.css` and `pure-nr-min.css` rollup files already include the Base
module.
@ -20,57 +20,63 @@ NEXT
### Base
* (!) Removed Normalize.css from checked-in `src/`. Bower is now used to
* __[!]__ Removed Normalize.css from checked-in `src/`. Bower is now used to
programmatically import Normalize.css into `bower_components/` if it's not
already installed. ([#160][])
already installed. Normalize.css is still bundled with Pure, this change is a
development-time change only. ([#160][])
### Buttons
* Removed `-webkit-font-smoothing: antialiased` rule from Buttons and Forms.
Pure should not dictate sub-pixel font rendering, that should be left to
the person's browser settings and/or the developer. ([#170][] @dchest)
* Removed `-webkit-font-smoothing: antialiased` rule from Buttons. Pure should
not dictate sub-pixel font rendering, that should be left to the person's
browser settings and/or the developer. ([#170][] @dchest)
### Forms
* (!) Removed `forms-core.css`. This was a copy of Normalize.css' form related
styles. Now that Pure requires the Base module (which is Normalize.css) to be
* __[!]__ Removed `forms-core.css`. This was a copy of Normalize.css' form
related styles. Now that Pure requires the Base module (Normalize.css) to be
on the page, the Forms Core submodule is no longer needed. ([#160][])
* Added `:focus` styles to `[readonly]` `<input>` elements. ([#143][])
* Removed `-webkit-font-smoothing: antialiased` rule from Forms input styles.
Pure should not dictate sub-pixel font rendering, that should be left to the
person's browser settings and/or the developer. ([#185][] @dchest)
### Grids
* Prevented grid units from falling to a new line on IE6 and IE7. Grid units now
have a separate `*width` value for oldIEs. This value is `0.005%` less than
the standard `width` value. This fix does not affect modern browsers. ([#154][])
* __[!]__ Improved Grids support with non-default fonts. This fixes issues with
custom fonts set either in a person's browser settings or by the developer
causing grids to break to a new line or overlap. The fix uses a specific font
stack on `.pure-g` and `.pure-g-r` classes to ensure the greatest OS/browser
compatibility. Now, by default grid units will now have
`font-family: sans-serif;` applied — this is the default font stack Pure's
Base module (Normalize.css) applies to the `<body>`.
This is a **breaking change** if you are using any non-default fonts in your
web project. Fortunately, it's quite easy to make sure your custom font stacks
apply to content within Pure Girds. Instead of applying your custom font to
only the `<body>` element, apply it to the grid units as well:
* Added a `height: auto` rule to images within a `.pure-g-r` so that their aspect
ratios are maintained when the page is resized. ([#172][]: @dchest)
```css
body,
.pure-g [class *= "pure-u"],
.pure-g-r [class *= "pure-u"] {
/* Set you're content font stack here: */
font-family: Georgia, Times, "Times New Roman", serif;
}
```
* (!) Added the following font stack to `.pure-g, .pure-g-r` in order to prevent
grids from breaking in various target environments:
Refer to the [Grids Documentation][Grids-fonts] for more details on using
non-default fonts with Pure Grids. ([#41][] @adapterik @dannyfritz, @pandeiro)
```css
font-family: FreeSans, Arimo, "Droid Sans", Helvetica, Arial, sans-serif;
```
* Fixed grid units from falling to a new line on IE 6 and IE 7. Grid units now
have a separate `*width` value for these older versions of IE. This value is
`0.005%` less than the standard `width` value. This fix does not affect modern
browsers because it uses the star hack. ([#154][])
This is a *breaking* change. If you are using any non-default font in your project,
you will need to modify your CSS and add a `font-family` to the grid unit classes:
```css
.pure-g [class *= "pure-u"],
.pure-g-r [class *= "pure-u"] {
/* Add your font in here, whether it's a custom font or a normal font */
font-family: "Times New Roman", serif;
}
```
Refer to the [Grids Documentation][Grids] for more details on using
non-default fonts with Pure Grids.
([#41][] @dannyfritz, @pandeiro, and many others!)
* Added a `height: auto` rule to images within a `.pure-g-r` so that their
aspect ratios are maintained when the page is resized. ([#172][]: @dchest)
[#41]: https://github.com/yui/pure/issues/41
@ -79,8 +85,11 @@ NEXT
[#160]: https://github.com/yui/pure/issues/160
[#170]: https://github.com/yui/pure/issues/170
[#171]: https://github.com/yui/pure/issues/171
[#172]: https://github.com/yui/pure/issues/172
[#185]: https://github.com/yui/pure/issues/185
[Customize]: http://purecss.io/customize/
[Grids]: http://purecss.io/grids/
[Grids-fonts]: http://purecss.io/grids/#using-grids-with-custom-fonts
0.2.1 (2013-07-17)
@ -88,8 +97,8 @@ NEXT
### Forms
* (!) Made `[readonly]` `<input>`s look visually different to `[disabled]` and
regular `<input>`s. ([#102][]: @jaseg)
* __[!]__ Made `[readonly]` `<input>`s look visually different to `[disabled]`
and regular `<input>`s. ([#102][]: @jaseg)
* Fixed copy/paste bug that mapped text inputs to `.pure-form` instead of
`.pure-group`. The `.pure-form-group input` styles are now applied to all
@ -108,7 +117,7 @@ NEXT
### Grids
* (!) Changed `.pure-u-1` grid unit to now use `width: 100%` instead of
* __[!]__ Changed `.pure-u-1` grid unit to now use `width: 100%` instead of
`display: block` to achieve taking up the full width of its container. This
makes it easier to override and align since it's using `display: inline-block`
like the other grid units. ([#94][])
@ -118,9 +127,9 @@ NEXT
### Menus
* (!) Fixed broken styling of active paginator items by using Grids CSS rules to
layout items horizontally; this makes sure the active item isn't overlapped.
([#127][])
* __[!]__ Fixed broken styling of active paginator items by using Grids CSS
rules to layout items horizontally; this makes sure the active item isn't
overlapped. ([#127][])
### Tables
@ -143,10 +152,10 @@ NEXT
0.2.0 (2013-06-11)
------------------
* (!) Fixed accessibility mistake by removing `a:focus {outline: none;}` rule
from `buttons-core.css`.
* __[!]__ Fixed accessibility mistake by removing `a:focus {outline: none;}`
rule from `buttons-core.css`.
* (!) Improved `:focus` styles by applying the same rules that are used by
* __[!]__ Improved `:focus` styles by applying the same rules that are used by
`:hover` styles. When overriding Pure's `:hover` styles, be sure to include
`:focus` selectors as well.
@ -168,7 +177,7 @@ NEXT
### Forms
* (!) `.pure-help-inline` has been replaced with `.pure-form-message-inline`. We
* __[!]__ Replaced `.pure-help-inline` with `.pure-form-message-inline`. We
still support the older classname but it is deprecated and will be going away
in a future release. ([#32][]: @dannytatom)
@ -219,7 +228,7 @@ NEXT
0.1.0 (2013-05-24)
------------------
* (!) Initial public release.
* __[!]__ Initial public release.
* Upgraded Normalize.css to 1.1.2.
@ -243,9 +252,9 @@ NEXT
0.0.2 (2013-05-16)
------------------
* (!) Renamed to Pure.
* __[!]__ Renamed to Pure.
* (!) Renamed CSS classname prefix to `pure`.
* __[!]__ Renamed CSS classname prefix to `pure`.
* Preview release (2).