1# Release Notes
2
3## 0.3.10
4
5### Fixes
6
7- Fix sizing of children when the available_space < min_size (#407)
8
9## 0.3.9
10
11### Fixes
12
13- Fix caching bug where a cached result would sometimes be incorrectly used when the amount of available space increased (bevyengine/bevy#8111) and (bevyengine/bevy#8124)
14
15## 0.3.8
16
17### Fixes
18
19- Fix incorrect min-content size for `flex-wrap: wrap` nodes (bevyengine/bevy#8082)
20
21## 0.3.7
22
23### Fixes
24
25- Fix: Make `padding` and `border` floor node sizes (#372)
26- Fix: Prevent percentages contributing to min-content sizes (#388) (also fixes bevyengine/bevy#8017)
27
28## 0.3.6
29
30### Fixes
31
32- Fix: Ignore `align_content` when `flex_wrap` is set to `nowrap` (#383)
33
34## 0.3.5
35
36### Fixes
37
38- Fix `display: none` when it is set on a flexbox child (#380)
39- Fix `display: none` when it is set on a grid child (#381)
40
41## 0.3.4
42
43### Fixes
44
45- Fix `display: none` when it is set for the only node in the hierarchy (#377)
46
47## 0.3.3
48
49### Added
50
51- Added `enable_rounding` and `disable_rounding` methods to the `Taffy` struct which enable consumers of Taffy to obtain unrounded `f32` values for the computed layouts if they want them. Rounding remains enabled by default.
52
53### Fixes
54
55- Fixed rounding algorithm such that it never leaves gaps between adjacent nodes (#369)
56- Fixed compiling with the `grid` feature disabled (#370)
57- Fixed compiling with the `std` feature disabled
58
59## 0.3.2
60
61### Fixes
62
63- Allow partial nested values to be deserialized into a `Style` using the `serde` feature.
64
65## 0.3.1
66
67### Fixes
68
69- The `serde` feature now works when the `grid` feature is enabled
70
71## 0.3.0
72
73### Highlights
74
75- [CSS Grid algorithm support](#new-feature-css-grid)
76- [Style helper functions](#new-feature-style-helpers)
77
78See below for details of breaking changes.
79
80### New Feature: CSS Grid
81
82We 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`.
83
84#### Learning Resources
85
86Taffy 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:
87
88- [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.
89- [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.
90
91#### Supported Features & Properties
92
93In addition to the usual sizing/spacing proerties (size, min_size, padding, margin, etc), the following Grid style properties are supported on Grid Containers:
94
95| Property                  | Explanation                                                                                    |
96| ---                       | ---                                                                                            |
97| [`grid-template-columns`] | The track sizing functions of the grid's explicit columns                                      |
98| [`grid-template-rows`]    | The track sizing functions of the grid's explicit rows                                         |
99| [`grid-auto-rows`]        | Track sizing functions for the grid's implicitly generated rows                                |
100| [`grid-auto-columns`]     | Track sizing functions for the grid's implicitly generated columns                             |
101| [`grid-auto-flow`]        | Whether auto-placed items are placed row-wise or column-wise. And sparsely or densely.         |
102| [`gap`]                   | The size of the vertical and horizontal gaps between grid rows/columns                         |
103| [`align-content`]         | Align grid tracks within the container in the inline (horizontal) axis                         |
104| [`justify-content`]       | Align grid tracks within the container in the block (vertical) axis                            |
105| [`align-items`]           | Align the child items within their grid areas in the inline (horizontal) axis                  |
106| [`justify-items`]         | Align the child items within their grid areas in the block (vertical) axis                     |
107
108And the following Grid style properties are supported on Grid Items (children):
109
110| Property                  | Explanation                                                                                    |
111| ---                       | ---                                                                                            |
112| [`grid-row`]              | The (row) grid line the item starts at (or a span)                                             |
113| [`grid-column`]           | The (column) grid line the item end at (or a span)                                             |
114| [`align-self`]            | Align the item within it's grid area in the inline (horizontal) axis. Overrides `align-items`. |
115| [`justify-self`]          | Align the item within it's grid area in the block (vertical) axis. Overrides `justify-items`.  |
116
117[`grid-template-columns`]: https://developer.mozilla.org/en-US/docs/Web/CSS/grid-template-columns
118[`grid-template-rows`]: https://developer.mozilla.org/en-US/docs/Web/CSS/grid-template-rows
119[`grid-auto-rows`]: https://developer.mozilla.org/en-US/docs/Web/CSS/grid-auto-rows
120[`grid-auto-columns`]: https://developer.mozilla.org/en-US/docs/Web/CSS/grid-auto-columns
121[`grid-auto-flow`]: https://developer.mozilla.org/en-US/docs/Web/CSS/grid-auto-flow
122[`gap`]: https://developer.mozilla.org/en-US/docs/Web/CSS/gap
123[`align-content`]: https://developer.mozilla.org/en-US/docs/Web/CSS/align_content
124[`justify-content`]: https://developer.mozilla.org/en-US/docs/Web/CSS/justify_content
125[`align-items`]: https://developer.mozilla.org/en-US/docs/Web/CSS/align-items
126[`justify-items`]: https://developer.mozilla.org/en-US/docs/Web/CSS/justify-items
127[`grid-row`]: https://developer.mozilla.org/en-US/docs/Web/CSS/grid-row
128[`grid-column`]: https://developer.mozilla.org/en-US/docs/Web/CSS/grid-column
129[`align-self`]: https://developer.mozilla.org/en-US/docs/Web/CSS/align-self
130[`justify-self`]: https://developer.mozilla.org/en-US/docs/Web/CSS/justify-self
131
132The following properties and features are not currently supported:
133
134- Subgrids
135- Masonry grid layout
136- Named grid lines
137- Named areas: `grid-template-areas` and `grid-area`
138- `grid-template` or `grid` shorthand
139
140#### Example
141
142See [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:
143
144```bash
145cargo run --example grid_holy_grail --features grid
146```
147
148### New Feature: Style Helpers
149
150Ten 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.
151
152For example, instead of:
153
154```rust
155let size : Size<Dimension> = Size { width: Dimension::Points(100.0), height: Dimension::Percent(50.0) };
156```
157
158you can now write
159
160```rust
161let size : Size<Dimension> = Size { width: points(100.0), height: percent(50.0) };
162```
163
164And 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
165
166```rust
167let size : Size<Dimension> = points(100.0);
168```
169
170Available style helpers:
171
172<table>
173  <thead><tr><th>Type(s)</th><th colspan="2">Helpers that work with that type</th></tr></thead>
174  <tbody>
175    <tr>
176      <td rowspan="3"><code>LengthPercentage</code></td>
177      <td><code>zero()</code></td>
178      <td>Generates a <code>Points</code> variant with the value <code>0.0</code></td>
179    </tr>
180    <tr>
181      <td><code>points(val:&nbsp;f32)</code></td>
182      <td>Generates a <code>Points</code> variant with the specified value</td>
183    </tr>
184    <tr>
185      <td><code>percent(val:&nbsp;f32)</code></td>
186      <td>Generates a <code>Percent</code> variant with the specified value.<br />Note that the scale of 0-1 not 0-100.</td>
187    </tr>
188    <tr>
189      <td rowspan="2"><code>LengthPercentageAuto</code><br /><code>Dimension</code></td>
190      <td colspan="2"><i>All helpers from <code>LengthPercentage</code> and...</i></td>
191    </tr>
192    <tr>
193      <td><code>auto()</code></td>
194      <td>Generates an <code>Auto</code> variant</td>
195    </tr>
196    <tr>
197      <td rowspan="3"><code>MinTrackSizingFunction</code></td>
198      <td colspan="2"><i>All helpers from <code>LengthPercentageAuto</code>/<code>Dimension</code> and...</i></td>
199    </tr>
200    <tr>
201      <td><code>min_content()</code></td>
202      <td>Generates an <code>MinContent</code> variant</td>
203    </tr>
204      <tr>
205      <td><code>max_content()</code></td>
206      <td>Generates an <code>MinContent</code> variant</td>
207    </tr>
208    <tr>
209      <td rowspan="3"><code>MaxTrackSizingFunction</code></td>
210      <td colspan="2"><i>All helpers from <code>MinTrackSizingFunction</code> and...</i></td>
211    </tr>
212    <tr>
213      <td><code>fit_content(limit:&nbsp;LengthPercentage)</code></td>
214      <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>
215    </tr>
216      <tr>
217      <td><code>fr(fraction:&nbsp;f32)</code></td>
218      <td>Generates a <code>Fraction</code> (<code>fr</code>) variant with the specified flex fraction </td>
219    </tr>
220    <tr>
221      <td rowspan="3"><code>NonRepeatingTrackSizingFunction</code></td>
222      <td colspan="2"><i>All helpers from <code>MaxTrackSizingFunction</code> and...</i></td>
223    </tr>
224    <tr>
225      <td><code>minmax(min: MinTrackSizingFunction, max: MaxTrackSizingFunction)</code></td>
226      <td>Equivalent to CSS <code>minmax()</code> function.</td>
227    </tr>
228    <tr>
229      <td><code>flex(fraction:&nbsp;f32)</code></td>
230      <td>Equivalent to CSS <code>minmax(0px, 1fr)</code>. This is likely what you want if you want evenly sized rows/columns.</td>
231    </tr>
232    <tr>
233      <td rowspan="2"><code>TrackSizingFunction</code></td>
234      <td colspan="2"><i>All helpers from <code>NonRepeatingTrackSizingFunction</code> and...</i></td>
235    </tr>
236    <tr>
237      <td><code>repeat(rep: GridTrackRepetition, tracks: Vec&lt;TrackSizingFunction&gt;)</code></td>
238      <td>Equivalent to css <code>repeat()</code> function.</td>
239    </tr>
240    <tr>
241      <td><code>Vec&lt;TrackSizingFunction&gt;</code></td>
242      <td><code>evenly_sized_tracks(count:&nbsp;u16)</code></td>
243      <td>Equivalent to CSS <code>repeat(count, minmax(0px, 1fr)</code></td>
244    </tr>
245    <tr>
246      <td rowspan="3"><code>AvailableSpace</code></td>
247      <td><code>auto()</code></td>
248      <td>Generates an <code>Auto</code> variant</td>
249    </tr>
250    <tr>
251      <td><code>min_content()</code></td>
252      <td>Generates an <code>MinContent</code> variant</td>
253    </tr>
254      <tr>
255      <td><code>max_content()</code></td>
256      <td>Generates an <code>MinContent</code> variant</td>
257    </tr>
258    <tr>
259      <td><code>Size&lt;T&gt;</code></td>
260      <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>
261    </tr>
262    <tr>
263      <td><code>Rect&lt;T&gt;</code></td>
264      <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>
265    </tr>
266  </tbody>
267</table>
268
269### Breaking API changes
270
271#### Changes to alignment style types
272
273- `AlignContent` and `JustifyContent` has been merged.
274  - `JustifyContent` is now an alias of `AlignContent` and contains the `Stretch` variant.
275  - This variant will be *ignored* (falling back to `Start`) when applied Flexbox containers. It is valid value for Grid containers.
276- `AlignItems` and `AlignSelf` have been merged.
277  - The `Auto` variant of `AlignSelf` has been removed. You should now use `Option::None` if you wish to specify `AlignSelf::Auto`.
278  - `AlignSelf` is now an alias of `AlignItems`.
279  - `JustifyItems` and `JustifySelf` aliases have been added. These properties have no affect on Flexbox containers, but apply to Grid containers.
280- `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.
281
282#### Strict style types
283
284- New types `LengthPercentage` and `LengthPercentageAuto` have been added.
285  - `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.
286  - `LengthPercentageAuto` is currently identical to `Dimension` but will allow us to expand dimension in future to support values like `MinContent`, `MaxContent` and `FitContent`.
287- 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).
288
289#### Position properties renamed
290
291- 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)
292- 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`.
293
294#### Changes to `LayoutTree`
295
296- Added generic associated type to `LayoutTree` for a `ChildIter`, an iterator on the children of a given node.
297- 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.
298- 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.
299- Added `is_childless` method to `LayoutTree` for querying whether a node has no children.
300
301#### `AvailableSpace` has been moved
302
303The `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.
304
305### Fixes
306
307- Flexbox nodes sized under a min-content constraint now size correctly (#291)
308- Aspect ratio is now applied correctly in many circumstances
309- Absolutely positioned items now apply margins correctly
310- Min/max size are now applied correctly
311- Inset applied incorrectly to relatively positioned flexbox children when both `top` and `bottom` or `left` and `right` were specified (#348)
312- 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)
313
314### Removed
315
316- 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.
317- 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.
318- 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.
319
320## 0.2.2
321
322### Fixes
323
324- Border or padding on the horizontal axis could, in some cases, increase the height of nodes.
325
326## 0.2.1
327
328### Fixes
329
330- 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`.
331- `taffy::compute_layout` has been made public allowing Taffy to be used with custom storage (#263)
332
333## 0.2.0
334
335### New features
336
337#### Flexbox "gap" and `AlignContent::SpaceEvenly`
338
339The [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.
340
341Additionally 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)
342
343#### Debug module and cargo feature
344
345Two debugging features have been added:
346
347- `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.
348- A cargo feature `debug`. This enabled debug logging of the layout computation process itself (this is probably mainly useful for those working taffy itself).
349
350### Performance improvements
351
352A number of performance improvements have landed since taffy 0.1:
353
354- 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%.
355- 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!
356
357#### Benchmarks vs. Taffy 0.1
358
359| Benchmark                                 | Taffy 0.1 | Taffy 0.2 | % change (0.1 -> 0.2) |
360| ---                                       | ---       | ---       | ---                   |
361| wide/1_000 nodes (2-level hierarchy)      | 699.18 µs | 445.01 µs | -36.279%              |
362| wide/10_000 nodes (2-level hierarchy)     | 8.8244 ms | 7.1313 ms | -16.352%              |
363| wide/100_000 nodes (2-level hierarchy)    | 204.48 ms | 242.93 ms | +18.803%              |
364| deep/4000 nodes (12-level hierarchy))     | 5.2320 s  | 2.7363 ms | -99.947%              |
365| deep/10_000 nodes (14-level hierarchy)    | 75.207 s  | 6.9415 ms | -99.991%              |
366| deep/100_000 nodes (17-level hierarchy)   | -         | 102.72 ms | -                     |
367| deep/1_000_000 nodes (20-level hierarchy) | -         | 799.35 ms | -                     |
368
369(note that the table above contains multiple different units (milliseconds vs. microseconds vs. nanoseconds))
370
371As 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.
372
373However, 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.
374
375#### Benchmarks vs. [Yoga](https://github.com/facebook/yoga)
376
377Yoga 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.
378
379| Benchmark | Yoga | Taffy 0.2 |
380| --- | --- | --- |
381| yoga/10 nodes (1-level hierarchy) | 45.1670 µs | 33.297 ns |
382| yoga/100 nodes (2-level hierarchy) | 134.1250 µs | 336.53 ns |
383| yoga/1_000 nodes (3-level hierarchy) | 1.2221 ms | 3.8928 µs |
384| yoga/10_000 nodes (4-level hierarchy) | 13.8672 ms | 36.162 µs |
385| yoga/100_000 nodes (5-level hierarchy) | 141.5307 ms | 1.6404 ms |
386
387(note that the table above contains multiple different units (milliseconds vs. microseconds vs. nanoseconds))
388
389While 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!
390
391### Breaking API changes
392
393#### Node creation changes
394
395- `taffy::Node` is now unique only to the Taffy instance from which it was created.
396- Renamed `Taffy.new_node(..)` -> `Taffy.new_with_children(..)`
397- Renamed `Taffy.new_leaf()` -> `Taffy.new_leaf_with_measure()`
398- Added `taffy::node::Taffy.new_leaf()` which allows the creation of new leaf-nodes without having to supply a measure function
399
400#### Error handling/representation improvements
401
402- Renamed `taffy::Error` -> `taffy::error::TaffyError`
403- Replaced `taffy::error::InvalidChild` with a new `InvalidChild` variant of `taffy::error::TaffyError`
404- Replaced `taffy::error::InvalidNode` with a new `InvalidNode` variant of `taffy::error::TaffyError`
405- The following method new return `Err(TaffyError::ChildIndexOutOfBounds)` instead of panicking:
406  - `taffy::Taffy::remove_child_at_index`
407  - `taffy::Taffy::replace_child_at_index`
408  - `taffy::Taffy::child_at_index`
409- `Taffy::remove` now returns a `Result<usize, Error>`, to indicate if the operation was sucessful (and if it was, which ID was invalidated).
410
411#### Some uses of `Option<f32>` replaced with a new `AvailableSpace` enum
412
413A new enum `Taffy::layout::AvailableSpace` has been added.
414
415The definition looks like this:
416
417```rust
418/// The amount of space available to a node in a given axis
419pub enum AvailableSpace {
420    /// The amount of space available is the specified number of pixels
421    Definite(f32),
422    /// The amount of space available is indefinite and the node should be laid out under a min-content constraint
423    MinContent,
424    /// The amount of space available is indefinite and the node should be laid out under a max-content constraint
425    MaxContent,
426}
427```
428
429This 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`).
430
431And 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..
432
433#### Builder methods are now `const` where possible
434
435- Several convenience constants have been defined: notably `Style::DEFAULT`
436- `Size<f32>.zero()` is now `Size::<f32>::ZERO`
437- `Point<f32>.zero()` is now  `Point::<f32>::ZERO`
438- `Size::undefined()` is now `Size::NONE`
439
440#### Removals
441
442- 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%).
443- Removed `taffy::number::Number`. Use `Option<f32>` is used instead
444  - the associated public `MinMax` and `OrElse` traits have also been removed; these should never have been public
445- 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).
446
447### Fixes
448
449- Miscellaneous correctness fixes which align our implementation with Chrome:
450
451  - Nodes can only ever have one parent
452  - Fixed rounding of fractional values to follow latest Chrome - values are now rounded the same regardless of their position
453  - Fixed computing free space when using both `flex-grow` and a minimum size
454  - 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)
455  - `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
456- Taffy can now be vendored using `cargo-vendor` (README.md is now included in package).
457
458## 0.1.0
459
460### 0.1.0 Changed
461
462- the `order` field of `Layout` is now public, and describes the relative z-ordering of nodes
463- renamed crate from `stretch2` to `taffy`
464- updated to the latest version of all dependencies to reduce upstream pain caused by duplicate dependencies
465- renamed `stretch::node::Strech` -> `taffy::node::Taffy`
466
467### 0.1.0 Fixed
468
469- fixed feature strategy for `alloc` and `std`: these can now be compiled together, with `std`'s types taking priority
470
471### 0.1.0 Removed
472
473- removed Javascript / Kotlin / Swift bindings
474  - the maintainer team lacks expertise to keep these working
475  - more serious refactors are planned, and this will be challenging to keep working through that process
476  - if you are interested in helping us maintain bindings to other languages, [get in touch](https://github.com/DioxusLabs/taffy/discussions)!
477- 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)
478- removed the `Direction` and `Overflow` structs, and the corresponding `direction` and `overflow` fields from `Style`
479  - these had no effect in the current code base and were actively misleading
480
481## stretch2 0.4.3
482
483This is the final release of `stretch`: migrate to the crate named `taffy` for future fixes and features!
484
485These notes describe the differences between this release and `stretch` 0.3.2, the abandoned crate from which this library was forked.
486
487### Changed
488
489- updated [assorted dependencies](https://github.com/vislyhq/stretch/commit/a6491117379cea52dedc9584d892594a143e8cb0)
490
491### Fixed
492
493- fixed an exponential performance blow-up with deep nesting
494- fixed percent height values, which were using parent width
495- recomputing layout no longer moves children of non-zero-positioned parent
496- fixed broken Swift bindings