1# Release Notes
2
3## 0.3.2
4
5### Fixes
6
7- Allow partial nested values to be deserialized into a `Style` using the `serde` feature.
8
9## 0.3.1
10
11### Fixes
12
13- The `serde` feature now works when the `grid` feature is enabled
14
15## 0.3.0
16
17### Highlights
18
19- [CSS Grid algorithm support](#new-feature-css-grid)
20- [Style helper functions](#new-feature-style-helpers)
21
22See below for details of breaking changes.
23
24### New Feature: CSS Grid
25
26We very excited to report that we now have support for CSS Grid layout. This is in addition to the existing Flexbox layout support, and the two modes interoperate. You can set a node to use Grid layout by setting the `display` property to `Display::Grid`.
27
28#### Learning Resources
29
30Taffy implements the CSS Grid specification faithfully, so documentation designed for the web should translate cleanly to Taffy's implementation. If you are interested in learning how to use CSS Grid, we would recommend the following resources:
31
32- [CSS Grid Garden](https://cssgridgarden.com/). This is an interactive tutorial/game that allows you to learn the essential parts of CSS Grid in a fun engaging way.
33- [A Complete Guide To CSS Grid](https://css-tricks.com/snippets/css/complete-guide-grid/) by CSS Tricks. This is detailed guide with illustrations and comphrehensive written explanation of the different Grid propertie and how they work.
34
35#### Supported Features & Properties
36
37In addition to the usual sizing/spacing proerties (size, min_size, padding, margin, etc), the following Grid style properties are supported on Grid Containers:
38
39| Property                  | Explanation                                                                                    |
40| ---                       | ---                                                                                            |
41| [`grid-template-columns`] | The track sizing functions of the grid's explicit columns                                      |
42| [`grid-template-rows`]    | The track sizing functions of the grid's explicit rows                                         |
43| [`grid-auto-rows`]        | Track sizing functions for the grid's implicitly generated rows                                |
44| [`grid-auto-columns`]     | Track sizing functions for the grid's implicitly generated columns                             |
45| [`grid-auto-flow`]        | Whether auto-placed items are placed row-wise or column-wise. And sparsely or densely.         |
46| [`gap`]                   | The size of the vertical and horizontal gaps between grid rows/columns                         |
47| [`align-content`]         | Align grid tracks within the container in the inline (horizontal) axis                         |
48| [`justify-content`]       | Align grid tracks within the container in the block (vertical) axis                            |
49| [`align-items`]           | Align the child items within their grid areas in the inline (horizontal) axis                  |
50| [`justify-items`]         | Align the child items within their grid areas in the block (vertical) axis                     |
51
52And the following Grid style properties are supported on Grid Items (children):
53
54| Property                  | Explanation                                                                                    |
55| ---                       | ---                                                                                            |
56| [`grid-row`]              | The (row) grid line the item starts at (or a span)                                             |
57| [`grid-column`]           | The (column) grid line the item end at (or a span)                                             |
58| [`align-self`]            | Align the item within it's grid area in the inline (horizontal) axis. Overrides `align-items`. |
59| [`justify-self`]          | Align the item within it's grid area in the block (vertical) axis. Overrides `justify-items`.  |
60
61[`grid-template-columns`]: https://developer.mozilla.org/en-US/docs/Web/CSS/grid-template-columns
62[`grid-template-rows`]: https://developer.mozilla.org/en-US/docs/Web/CSS/grid-template-rows
63[`grid-auto-rows`]: https://developer.mozilla.org/en-US/docs/Web/CSS/grid-auto-rows
64[`grid-auto-columns`]: https://developer.mozilla.org/en-US/docs/Web/CSS/grid-auto-columns
65[`grid-auto-flow`]: https://developer.mozilla.org/en-US/docs/Web/CSS/grid-auto-flow
66[`gap`]: https://developer.mozilla.org/en-US/docs/Web/CSS/gap
67[`align-content`]: https://developer.mozilla.org/en-US/docs/Web/CSS/align_content
68[`justify-content`]: https://developer.mozilla.org/en-US/docs/Web/CSS/justify_content
69[`align-items`]: https://developer.mozilla.org/en-US/docs/Web/CSS/align-items
70[`justify-items`]: https://developer.mozilla.org/en-US/docs/Web/CSS/justify-items
71[`grid-row`]: https://developer.mozilla.org/en-US/docs/Web/CSS/grid-row
72[`grid-column`]: https://developer.mozilla.org/en-US/docs/Web/CSS/grid-column
73[`align-self`]: https://developer.mozilla.org/en-US/docs/Web/CSS/align-self
74[`justify-self`]: https://developer.mozilla.org/en-US/docs/Web/CSS/justify-self
75
76The following properties and features are not currently supported:
77
78- Subgrids
79- Masonry grid layout
80- Named grid lines
81- Named areas: `grid-template-areas` and `grid-area`
82- `grid-template` or `grid` shorthand
83
84#### Example
85
86See [examples/grid_holy_grail.rs](https://github.com/DioxusLabs/taffy/blob/main/examples/grid_holy_grail.rs) for an example using Taffy to implement the so-called [Holy Grail Layout](https://en.wikipedia.org/wiki/Holy_grail_(web_design)). If you want to run this example, the don't forget the enable the CSS Grid cargo feature:
87
88```bash
89cargo run --example grid_holy_grail --features grid
90```
91
92### New Feature: Style Helpers
93
94Ten new helper functions have added to the taffy prelude. These helper functions have short, intuitive names, and have generic return types which allow them to magically return the correct type depending on context. They make defining styles much easier, and means you won't typically need to use types like `Dimension` or `TrackSizingFunction` directly.
95
96For example, instead of:
97
98```rust
99let size : Size<Dimension> = Size { width: Dimension::Points(100.0), height: Dimension::Percent(50.0) };
100```
101
102you can now write
103
104```rust
105let size : Size<Dimension> = Size { width: points(100.0), height: percent(50.0) };
106```
107
108And that same helper function will work other types like `LengthPercentage` and `MinTrackSizingFunction` that also have a `Points` variant. There are also generic impl's for `Size<T>`, `Rect<T>` and `Line<T>` which means if your node is the same size in all dimensions you can even write
109
110```rust
111let size : Size<Dimension> = points(100.0);
112```
113
114Available style helpers:
115
116<table>
117  <thead><tr><th>Type(s)</th><th colspan="2">Helpers that work with that type</th></tr></thead>
118  <tbody>
119    <tr>
120      <td rowspan="3"><code>LengthPercentage</code></td>
121      <td><code>zero()</code></td>
122      <td>Generates a <code>Points</code> variant with the value <code>0.0</code></td>
123    </tr>
124    <tr>
125      <td><code>points(val:&nbsp;f32)</code></td>
126      <td>Generates a <code>Points</code> variant with the specified value</td>
127    </tr>
128    <tr>
129      <td><code>percent(val:&nbsp;f32)</code></td>
130      <td>Generates a <code>Percent</code> variant with the specified value.<br />Note that the scale of 0-1 not 0-100.</td>
131    </tr>
132    <tr>
133      <td rowspan="2"><code>LengthPercentageAuto</code><br /><code>Dimension</code></td>
134      <td colspan="2"><i>All helpers from <code>LengthPercentage</code> and...</i></td>
135    </tr>
136    <tr>
137      <td><code>auto()</code></td>
138      <td>Generates an <code>Auto</code> variant</td>
139    </tr>
140    <tr>
141      <td rowspan="3"><code>MinTrackSizingFunction</code></td>
142      <td colspan="2"><i>All helpers from <code>LengthPercentageAuto</code>/<code>Dimension</code> and...</i></td>
143    </tr>
144    <tr>
145      <td><code>min_content()</code></td>
146      <td>Generates an <code>MinContent</code> variant</td>
147    </tr>
148      <tr>
149      <td><code>max_content()</code></td>
150      <td>Generates an <code>MinContent</code> variant</td>
151    </tr>
152    <tr>
153      <td rowspan="3"><code>MaxTrackSizingFunction</code></td>
154      <td colspan="2"><i>All helpers from <code>MinTrackSizingFunction</code> and...</i></td>
155    </tr>
156    <tr>
157      <td><code>fit_content(limit:&nbsp;LengthPercentage)</code></td>
158      <td>Generates a <code>FitContent</code> variant with the specified limit.<br />Nest the <code>points</code> or <code>percent</code> helper inside this function to specified the limit.</td>
159    </tr>
160      <tr>
161      <td><code>fr(fraction:&nbsp;f32)</code></td>
162      <td>Generates a <code>Fraction</code> (<code>fr</code>) variant with the specified flex fraction </td>
163    </tr>
164    <tr>
165      <td rowspan="3"><code>NonRepeatingTrackSizingFunction</code></td>
166      <td colspan="2"><i>All helpers from <code>MaxTrackSizingFunction</code> and...</i></td>
167    </tr>
168    <tr>
169      <td><code>minmax(min: MinTrackSizingFunction, max: MaxTrackSizingFunction)</code></td>
170      <td>Equivalent to CSS <code>minmax()</code> function.</td>
171    </tr>
172    <tr>
173      <td><code>flex(fraction:&nbsp;f32)</code></td>
174      <td>Equivalent to CSS <code>minmax(0px, 1fr)</code>. This is likely what you want if you want evenly sized rows/columns.</td>
175    </tr>
176    <tr>
177      <td rowspan="2"><code>TrackSizingFunction</code></td>
178      <td colspan="2"><i>All helpers from <code>NonRepeatingTrackSizingFunction</code> and...</i></td>
179    </tr>
180    <tr>
181      <td><code>repeat(rep: GridTrackRepetition, tracks: Vec&lt;TrackSizingFunction&gt;)</code></td>
182      <td>Equivalent to css <code>repeat()</code> function.</td>
183    </tr>
184    <tr>
185      <td><code>Vec&lt;TrackSizingFunction&gt;</code></td>
186      <td><code>evenly_sized_tracks(count:&nbsp;u16)</code></td>
187      <td>Equivalent to CSS <code>repeat(count, minmax(0px, 1fr)</code></td>
188    </tr>
189    <tr>
190      <td rowspan="3"><code>AvailableSpace</code></td>
191      <td><code>auto()</code></td>
192      <td>Generates an <code>Auto</code> variant</td>
193    </tr>
194    <tr>
195      <td><code>min_content()</code></td>
196      <td>Generates an <code>MinContent</code> variant</td>
197    </tr>
198      <tr>
199      <td><code>max_content()</code></td>
200      <td>Generates an <code>MinContent</code> variant</td>
201    </tr>
202    <tr>
203      <td><code>Size&lt;T&gt;</code></td>
204      <td colspan="2">Any helper that works for <code>T</code> will also work for <code>Size&lt;T&gt;</code> and will set both <code>width</code> and <code>height</code> to that value</td>
205    </tr>
206    <tr>
207      <td><code>Rect&lt;T&gt;</code></td>
208      <td colspan="2">Any helper that works for <code>T</code> will also work for <code>Rect&lt;T&gt;</code> and will set <code>top</code>, <code>left</code>, <code>bottom</code>, and <code>right</code> to that value</td>
209    </tr>
210  </tbody>
211</table>
212
213### Breaking API changes
214
215#### Changes to alignment style types
216
217- `AlignContent` and `JustifyContent` has been merged.
218  - `JustifyContent` is now an alias of `AlignContent` and contains the `Stretch` variant.
219  - This variant will be *ignored* (falling back to `Start`) when applied Flexbox containers. It is valid value for Grid containers.
220- `AlignItems` and `AlignSelf` have been merged.
221  - The `Auto` variant of `AlignSelf` has been removed. You should now use `Option::None` if you wish to specify `AlignSelf::Auto`.
222  - `AlignSelf` is now an alias of `AlignItems`.
223  - `JustifyItems` and `JustifySelf` aliases have been added. These properties have no affect on Flexbox containers, but apply to Grid containers.
224- `Default` impls have been removed from all alignment types. This is because the correct default varies by property, and the types are now shared between multiple properties. The `Style` struct still has a default for each alignment property, so this is considered unlikely to affect you in practice.
225
226#### Strict style types
227
228- New types `LengthPercentage` and `LengthPercentageAuto` have been added.
229  - `LengthPercentage` is like `Dimension` but only contains the `Points` and `Percent` variants, which allows us to increase type safety for properties that don't support the `Auto` value.
230  - `LengthPercentageAuto` is currently identical to `Dimension` but will allow us to expand dimension in future to support values like `MinContent`, `MaxContent` and `FitContent`.
231- Some style properties have been updated to use either `LengthPercentage` or `LengthPercentageAuto` instead of `Dimension`. You will need to update your code, but it is recommended that you use the new style helpers (see above) rather than using the new types directly (although you certainly can use them directly if you want to).
232
233#### Position properties renamed
234
235- The `position` property is now renamed to `inset` and is now in line with [CSS inset specs](https://developer.mozilla.org/en-US/docs/Web/CSS/inset)
236- The `position_type` property is now renamed to `position` and is now in line with [CSS position specs](https://developer.mozilla.org/en-US/docs/Web/CSS/position). The `PositionType` enum has been similarly renamed to `Position`.
237
238#### Changes to `LayoutTree`
239
240- Added generic associated type to `LayoutTree` for a `ChildIter`, an iterator on the children of a given node.
241- Changed the `children` method of `LayoutTree` to return the `ChildIter` generic associated type to allow for custom tree storage implementations which do not store the children of a node contiguously.
242- Added `child_count`  method to `LayoutTree` for querying the number of children of a node. Required because the `children` method now returns an iterator instead of an array.
243- Added `is_childless` method to `LayoutTree` for querying whether a node has no children.
244
245#### `AvailableSpace` has been moved
246
247The `AvailableSpace` enum has been moved from the `layout` module to the `style` module. If you are importing it via the prelude then you will unaffected by the change.
248
249### Fixes
250
251- Flexbox nodes sized under a min-content constraint now size correctly (#291)
252- Aspect ratio is now applied correctly in many circumstances
253- Absolutely positioned items now apply margins correctly
254- Min/max size are now applied correctly
255- Inset applied incorrectly to relatively positioned flexbox children when both `top` and `bottom` or `left` and `right` were specified (#348)
256- Fix case where column-gap style could be used in place of row-gap style (when using a percentage gap with an indefinite container size)
257
258### Removed
259
260- Removed `top_from_points`, `bot_from_points`, `top_from_percent`, and `bot_from_percent` methods removed from `Rect<Dimension>`. These functions were incredibly specific for an unusual use case, so we would be surprised if anyone was using them. Please use the new style helpers instead.
261- Removed `min_main_size`, `max_main_size`, `min_cross_size`, `max_cross_size`, and `cross_size` methods from `Style`. Use the more general `cross` and `main` methods directly on the `size`, `min_size`, and `max_size` properties instead.
262- Removed `main_margin_start`, `main_margin_end`, `cross_margin_start`, `cross_margin_end` from `Style`. Use the more general `main_start`, `main_end`, `cross_start`, and `cross_end` on the `margin` property instead.
263
264## 0.2.2
265
266### Fixes
267
268- Border or padding on the horizontal axis could, in some cases, increase the height of nodes.
269
270## 0.2.1
271
272### Fixes
273
274- In case of conflicts, `min_size` now overrides `max_size` which overrides `size` (#261). This is the behaviour specified in the CSS specification, and was also the behaviour in Taffy `v0.1.0`, but a regression was introduced in Taffy `v0.2.0`.
275- `taffy::compute_layout` has been made public allowing Taffy to be used with custom storage (#263)
276
277## 0.2.0
278
279### New features
280
281#### Flexbox "gap" and `AlignContent::SpaceEvenly`
282
283The [gap](https://developer.mozilla.org/en-US/docs/Web/CSS/gap) property is now supported on flex containers. This can make it much easier to create even spacing or "gutters" between nodes.
284
285Additionally we have a `SpaceEvenly` variant to the `AlignContent` enum to support evenly spaced justification in the cross axis (equivalent to  `align-content: space-evenly` in CSS)
286
287#### Debug module and cargo feature
288
289Two debugging features have been added:
290
291- `taffy::debug::print_tree(&Taffy, root)` - This will print a debug representation of the computed layout of an entire node tree (starting at `root`), which can be useful for debugging layouts.
292- A cargo feature `debug`. This enabled debug logging of the layout computation process itself (this is probably mainly useful for those working taffy itself).
293
294### Performance improvements
295
296A number of performance improvements have landed since taffy 0.1:
297
298- Firstly, our custom `taffy::forest` storage implementation was ripped out and replaced with a much simpler implementation using the `slotmap` crate. This led to performance increases of up to 90%.
299- Secondly, the caching implementation was improved by upping the number of cache slots from 2 to 4 and tweaking how computed results are allocated to chache slots to better match the actual usage patterns of the flexbox layout algorithm. This had a particularly dramatic effect on deep hierachies (which often involve recomputing the same results repeatedly), fixing the exponential blowup that was previously exhibited on these trees and improving performance by over 1000x in some cases!
300
301#### Benchmarks vs. Taffy 0.1
302
303| Benchmark                                 | Taffy 0.1 | Taffy 0.2 | % change (0.1 -> 0.2) |
304| ---                                       | ---       | ---       | ---                   |
305| wide/1_000 nodes (2-level hierarchy)      | 699.18 µs | 445.01 µs | -36.279%              |
306| wide/10_000 nodes (2-level hierarchy)     | 8.8244 ms | 7.1313 ms | -16.352%              |
307| wide/100_000 nodes (2-level hierarchy)    | 204.48 ms | 242.93 ms | +18.803%              |
308| deep/4000 nodes (12-level hierarchy))     | 5.2320 s  | 2.7363 ms | -99.947%              |
309| deep/10_000 nodes (14-level hierarchy)    | 75.207 s  | 6.9415 ms | -99.991%              |
310| deep/100_000 nodes (17-level hierarchy)   | -         | 102.72 ms | -                     |
311| deep/1_000_000 nodes (20-level hierarchy) | -         | 799.35 ms | -                     |
312
313(note that the table above contains multiple different units (milliseconds vs. microseconds vs. nanoseconds))
314
315As you can see, we have actually regressed slightly in the "wide" benchmarks (where all nodes are siblings of a single parent node). Although it should be noted our results in these benchmarks are still very fast, especially on the 10,000 node benchmark which we consider to be the most realistic size where the result is measured in microseconds.
316
317However, in the "deep" benchmarks we see dramatic improvements. The previous version of Taffy suffered from exponential blowup in the case of deeply nested hierachies. This has resulted in somewhat silly improvements like the 10,000 node (14-level) hierachy where Taffy 0.2 is a full 1 million times faster than Taffy 0.1. We've also included results with larger numbers of nodes (although you're unlikely to need that many) to demonstrate that this scalability continues up to even deeper levels of nesting.
318
319#### Benchmarks vs. [Yoga](https://github.com/facebook/yoga)
320
321Yoga benchmarks run via it's node.js bindings (the `yoga-layout-prebuilt` npm package), they were run a few times manually and it was verified that variance in the numbers of each run was minimal. It should be noted that this is using an old version of Yoga.
322
323| Benchmark | Yoga | Taffy 0.2 |
324| --- | --- | --- |
325| yoga/10 nodes (1-level hierarchy) | 45.1670 µs | 33.297 ns |
326| yoga/100 nodes (2-level hierarchy) | 134.1250 µs | 336.53 ns |
327| yoga/1_000 nodes (3-level hierarchy) | 1.2221 ms | 3.8928 µs |
328| yoga/10_000 nodes (4-level hierarchy) | 13.8672 ms | 36.162 µs |
329| yoga/100_000 nodes (5-level hierarchy) | 141.5307 ms | 1.6404 ms |
330
331(note that the table above contains multiple different units (milliseconds vs. microseconds vs. nanoseconds))
332
333While we're trying not to get too excited (there could easily be an issue with our benchmarking methodology which make this an unfair comparison), we are pleased to see that we seem to be anywhere between 100x and 1000x times faster depending on the node count!
334
335### Breaking API changes
336
337#### Node creation changes
338
339- `taffy::Node` is now unique only to the Taffy instance from which it was created.
340- Renamed `Taffy.new_node(..)` -> `Taffy.new_with_children(..)`
341- Renamed `Taffy.new_leaf()` -> `Taffy.new_leaf_with_measure()`
342- Added `taffy::node::Taffy.new_leaf()` which allows the creation of new leaf-nodes without having to supply a measure function
343
344#### Error handling/representation improvements
345
346- Renamed `taffy::Error` -> `taffy::error::TaffyError`
347- Replaced `taffy::error::InvalidChild` with a new `InvalidChild` variant of `taffy::error::TaffyError`
348- Replaced `taffy::error::InvalidNode` with a new `InvalidNode` variant of `taffy::error::TaffyError`
349- The following method new return `Err(TaffyError::ChildIndexOutOfBounds)` instead of panicking:
350  - `taffy::Taffy::remove_child_at_index`
351  - `taffy::Taffy::replace_child_at_index`
352  - `taffy::Taffy::child_at_index`
353- `Taffy::remove` now returns a `Result<usize, Error>`, to indicate if the operation was sucessful (and if it was, which ID was invalidated).
354
355#### Some uses of `Option<f32>` replaced with a new `AvailableSpace` enum
356
357A new enum `Taffy::layout::AvailableSpace` has been added.
358
359The definition looks like this:
360
361```rust
362/// The amount of space available to a node in a given axis
363pub enum AvailableSpace {
364    /// The amount of space available is the specified number of pixels
365    Definite(f32),
366    /// The amount of space available is indefinite and the node should be laid out under a min-content constraint
367    MinContent,
368    /// The amount of space available is indefinite and the node should be laid out under a max-content constraint
369    MaxContent,
370}
371```
372
373This enum is now used instead of `Option<f32>` when calling `Taffy.compute_layout` (if you previously passing `Size::NONE` to `compute_layout`, then you will need to change this to `Size::MAX_CONTENT`).
374
375And a different instance of it is passed as a new second parameter to `MeasureFunc`. `MeasureFunc`s may choose to use this parameter in their computation or ignore it as they see fit. The canonical example of when it makes sense to use it is when laying out text. If `MinContent` has been passed in the axis in which the text is flowing (i.e. the horizontal axis for left-to-right text), then you should line-break at every possible opportunity (e.g. all word boundaries), whereas if `MaxContent` has been passed then you shouldn't line break at all..
376
377#### Builder methods are now `const` where possible
378
379- Several convenience constants have been defined: notably `Style::DEFAULT`
380- `Size<f32>.zero()` is now `Size::<f32>::ZERO`
381- `Point<f32>.zero()` is now  `Point::<f32>::ZERO`
382- `Size::undefined()` is now `Size::NONE`
383
384#### Removals
385
386- Removed `taffy::forest::Forest`. `taffy::node::Taffy` now handles it's own storage using a slotmap (which comes with a performance boost up to 90%).
387- Removed `taffy::number::Number`. Use `Option<f32>` is used instead
388  - the associated public `MinMax` and `OrElse` traits have also been removed; these should never have been public
389- Removed unused dependencies `hashbrown`, `hash32`, and `typenum`. `slotmap` is now the only required dependency (`num_traits` and `arrayvec` are also required if you wish to use taffy in a `no_std` environment).
390
391### Fixes
392
393- Miscellaneous correctness fixes which align our implementation with Chrome:
394
395  - Nodes can only ever have one parent
396  - Fixed rounding of fractional values to follow latest Chrome - values are now rounded the same regardless of their position
397  - Fixed computing free space when using both `flex-grow` and a minimum size
398  - Padding is now only subtracted when determining the available space if the node size is unspecified, following [section 9.2.2 of the flexbox spec](https://www.w3.org/TR/css-flexbox-1/#line-sizing)
399  - `MeasureFunc` (and hence `NodeData` and hence `Forest` and hence the public `Taffy` type) are now `Send` and `Sync`, enabling their use in async and parallel applications
400- Taffy can now be vendored using `cargo-vendor` (README.md is now included in package).
401
402## 0.1.0
403
404### 0.1.0 Changed
405
406- the `order` field of `Layout` is now public, and describes the relative z-ordering of nodes
407- renamed crate from `stretch2` to `taffy`
408- updated to the latest version of all dependencies to reduce upstream pain caused by duplicate dependencies
409- renamed `stretch::node::Strech` -> `taffy::node::Taffy`
410
411### 0.1.0 Fixed
412
413- fixed feature strategy for `alloc` and `std`: these can now be compiled together, with `std`'s types taking priority
414
415### 0.1.0 Removed
416
417- removed Javascript / Kotlin / Swift bindings
418  - the maintainer team lacks expertise to keep these working
419  - more serious refactors are planned, and this will be challenging to keep working through that process
420  - if you are interested in helping us maintain bindings to other languages, [get in touch](https://github.com/DioxusLabs/taffy/discussions)!
421- the `serde_camel_case` and `serde_kebab_case` features have been removed: they were poorly motivated and were not correctly additive (if both were enabled compilation would fail)
422- removed the `Direction` and `Overflow` structs, and the corresponding `direction` and `overflow` fields from `Style`
423  - these had no effect in the current code base and were actively misleading
424
425## stretch2 0.4.3
426
427This is the final release of `stretch`: migrate to the crate named `taffy` for future fixes and features!
428
429These notes describe the differences between this release and `stretch` 0.3.2, the abandoned crate from which this library was forked.
430
431### Changed
432
433- updated [assorted dependencies](https://github.com/vislyhq/stretch/commit/a6491117379cea52dedc9584d892594a143e8cb0)
434
435### Fixed
436
437- fixed an exponential performance blow-up with deep nesting
438- fixed percent height values, which were using parent width
439- recomputing layout no longer moves children of non-zero-positioned parent
440- fixed broken Swift bindings