patch: Fire the smallest (default) layout event when increasing the viewport…

v5.2.12

Fire the smallest (default) layout event when increasing the viewport…

patch: Fix `o-grid.layoutChange` for custom layouts (breakpoints)

Fix `o-grid.layoutChange` for custom layouts (breakpoints) (#287)

* Fix `o-grid.layoutChange` for custom layouts (breakpoints)

It is possible to add a custom layout (breakpoint) to the grid:
```scss
@include oGridAddLayout(
	$layout-name: XS,
	$layout-width: 360px
);
```

However the `enableLayoutChangeEvents` method, which sets up event listeners to fire
when layouts change, did not correctly fire for custom layouts. It fired layout change events
for any custom layout when the `default` layout change is fired, regardless of the size of the
custom layout.

Now events are fired correctly for each layout, however this still depends on each layout having
the same CSS unit (px, rem, etc). Since `oGridAddLayout` currently throws an error if there
is a mismatch of units I think that's ok.

https://github.com/Financial-Times/o-grid/issues/286

patch: Restore snappy mode (de-deprecate)

Restore snappy mode (de-deprecate) (#275)

The snappy grid is used in 3 important places on ft.com (not the app):
- front page
- stream page
- article page

There is no plan to update these pages at the moment to remove
the snappy grid, so the deprecation notice should be removed
as it is a nuisance and we will not be able to remove snappy
mode whilst it is still used by these pages. To deprecate
snappy mode in the future these pages must first be redesigned.
For example without the snappy grid stream page teasers may
become very long and difficult to read.

Closes: https://github.com/Financial-Times/o-grid/issues/201

patch: make the bookmarklet use the latest version of o-grid

v5.2.9

make the bookmarklet use the latest version of o-grid

patch: add extension to relative imports to make the code work directly in a browser

v5.2.8

add extension to relative imports to make the code work directly in a…

patch: Add general usage to readme

Add general usage to readme (#226)

Links to instructions on how to include Origami components. https://github.com/Financial-Times/origami/issues/59

patch: Remove snappy specific `$_o-grid-max-width` declaration.

Remove snappy specific `$_o-grid-max-width` declaration. (#220)

It uses the same value as the default `$_o-grid-max-width` variable
above it.

patch: Restore the deprecated snappy mode by default feature.

Restore the deprecated snappy mode by default feature. (#219)

It was deleted by mistake here:
https://github.com/Financial-Times/o-grid/commit/5fbe04f4debd3b387939e4b5578acc2198178665#diff-bec94ad455c1c6700d76b841e9984f7cL195

patch: Correct contact details in the readme

v5.2.4

Correct contact details in the readme (#218)

patch: Bump origami-ci-tools from 1.3.12 to 2.0.0

Bump origami-ci-tools from 1.3.12 to 2.0.0 (#215)

* Bump origami-ci-tools from 1.3.12 to 2.0.0

Bumps [origami-ci-tools](https://github.com/Financial-Times/origami-ci-tools) from 1.3.12 to 2.0.0.
- [Release notes](https://github.com/Financial-Times/origami-ci-tools/releases)
- [Commits](https://github.com/Financial-Times/origami-ci-tools/compare/v1.3.12...v2.0.0)

Signed-off-by: dependabot-preview[bot] <[email protected]>

* add stylelint config

* fix stylelint issues

* update to latest stylelint origami config

* fix stylelint issues

* fix stylelint issues

* update to latest stylelint origami config

* remove package-lock.json file

* update to latest Sass linting expectations

* create grid-is-responsive variable before using it

* Delete package-lock.json

* Update README.md

* Remove duplicate deprecation warning

* Restore order of `zoom: 1;` CSS line, so test expectations do not change

Co-authored-by: dependabot-preview[bot] <27856297+dependabot-preview[bot]@users.noreply.github.com>
Co-authored-by: Jake Champion <[email protected]>
Co-authored-by: chee <[email protected]>
Co-authored-by: notlee <[email protected]>
Co-authored-by: Jake Champion <[email protected]>