|
2 | 2 | CSS4J RELEASE NOTES |
3 | 3 | =================== |
4 | 4 |
|
5 | | -Release 1.0.4 - April 14, 2020 [End of Life - Unsupported] |
6 | | ----------------------------------------------------------- |
| 5 | +Release 1.0.5 - June 5, 2020 [This release is EOL and not formally supported] |
| 6 | +----------------------------------------------------------------------------- |
7 | 7 |
|
8 | 8 | Release Highlights |
9 | 9 | ------------------ |
10 | | - This release brings backports of a few important bug fixes to the 1.x branch, |
11 | | -although users should upgrade to 2.0 or later as soon as possible (1.x is not |
12 | | -formally maintained anymore). When upgrading, please keep in mind that 2.x |
13 | | -releases require Java 8 or higher. |
14 | | - |
15 | | - * The following is adapted from the 2.0.2 Release Notes: * |
16 | | - |
17 | | - This library handled font-size values a bit different than the other values. |
18 | | -When a font-size was expressed as a percentage, if the value of the parent font |
19 | | -size could not be accurately determined the value was left as a precentage in |
20 | | -the serialized style. This did not apply to computations that depended on the |
21 | | -font size, like 'em' values in 'margin' or 'padding' properties: in that case |
22 | | -default values were forced for that font size, and an absolute length was |
23 | | -obtained. |
24 | | - |
25 | | - This procedure allows easy inspection of the specified vaues, but is inadequate |
26 | | -when the serialized style is used as the input for other software packages. |
27 | | -Changes to the library were made in the past to address this, but percentages of |
28 | | -font-size values were kept. |
29 | | - |
30 | | - Not only the serialization is inadequate: it also introduces a degradation in |
31 | | -performance that can be highly noticeable with heavy documents (thousands of |
32 | | -nodes, several tens of thousand rules). So the serialization of computed font |
33 | | -sizes now avoids percentages: if you had unit tests depending on that, you may |
34 | | -have to change them. |
35 | | - |
36 | | - Other than that, this release comes with interesting fixes, including one for a |
37 | | -regression introduced in 1.0.3 (triggered by var() values inside gradients). All |
38 | | -users are encouraged to upgrade. |
| 10 | + This release brings backports of a few bug fixes to the 1.x branch, although |
| 11 | +users should upgrade to 2.0 or later as soon as possible (1.x is not formally |
| 12 | +maintained anymore). When upgrading, please keep in mind that 2.x releases |
| 13 | +require Java 8 or higher. |
| 14 | + |
| 15 | + All 1.0 users are encouraged to upgrade at least to this release. |
39 | 16 |
|
40 | 17 |
|
41 | 18 | Description |
|
0 commit comments