|
2 | 2 | CSS4J RELEASE NOTES |
3 | 3 | =================== |
4 | 4 |
|
5 | | -Release 3.4.0 - February 28, 2021 |
6 | | ---------------------------------- |
| 5 | +Release 3.5.0 - May 30, 2021 |
| 6 | +---------------------------- |
7 | 7 |
|
8 | 8 | Release Highlights |
9 | 9 | ------------------ |
10 | | -* Support for lab() and lch() color functions. |
11 | 10 |
|
12 | | - The lab() and lch() functions are finally landing in Webkit, and the other |
13 | | - major browsers have shown interest in implementing them (although it may still |
14 | | - take some time). |
| 11 | +* Gradle build. |
15 | 12 |
|
16 | | - The usage of these functions in a toolchain with the typical Java open source |
17 | | - tools (which tend to use the sRGB default color space) could be problematic, |
18 | | - as lab() and lch() are often specified out of that gamut, but an accurate RGB |
19 | | - clamping method is provided. |
20 | | - |
21 | | - |
22 | | -* Customizable serialization of computed styles. |
23 | | - |
24 | | - Now you can control the serialization of computed styles thanks to a new |
25 | | - factory method: |
26 | | - StyleFormattingFactory.createComputedStyleFormattingContext(), |
27 | | - which returns a DeclarationFormattingContext. |
28 | | - |
29 | | - A non-default implementation of that interface, called |
30 | | - RGBStyleFormattingFactory, is provided for the convenience of users that can |
31 | | - only deal with rgb colors in computed styles (for example those feeding CSS4J |
32 | | - computed styles into Apache FOP). Basically, it allows to use CSS with Lab, |
33 | | - LCh or Hsl colors and then convert them to RGB at the computed-style stage. |
34 | | - |
35 | | - |
36 | | -* CSSOM: make the old rgb(a) color functional serialization with commas the |
37 | | - default for color conversions to RGB. |
38 | | - |
39 | | - When parsing, the library uses the same RGB format that was specified. That |
40 | | - is, if the input was a rgba() function with commas, it serialized that way. |
41 | | - However, when other types of colors were converted to RGB, it defaulted to the |
42 | | - modern format without the commas. That default was not the most adequate |
43 | | - though: |
44 | | - |
45 | | - 1) According to the 2020 Web Almanac, "99.89% of functionally specified sRGB |
46 | | - colors are using the since-forever legacy format with commas [...] rather |
47 | | - than the new comma-less form". |
48 | | - |
49 | | - 2) XSL:FO uses the old format with commas, see |
50 | | - https://www.w3.org/TR/xsl/#expr-color-functions |
51 | | - |
52 | | - |
53 | | -* Added method match(CSSValueSyntax) to both LexicalUnit and CSSValue. |
54 | | - |
55 | | - This allows checking the grammar of values against specific syntaxes like |
56 | | - <length>+, <string>#, <transform-function> or <unicode-range>#. |
57 | | - |
58 | | - |
59 | | -* Support registered custom properties (including @property rules) from CSS |
60 | | - Properties and Values API Level 1. |
61 | | - |
62 | | - The rule (that currently only works in Chrome/Blink) allows to customize the |
63 | | - behaviour of custom properties. |
64 | | - |
65 | | - |
66 | | -* DOM: add the DOMNode.removeAllChild() convenience method. |
67 | | - |
68 | | - AFAIK no other DOM implementation contains this useful method. |
| 13 | + The project is now built by Gradle instead of Maven. It is no longer necessary |
| 14 | + to manually install the dependencies that are not available in Maven Central. |
69 | 15 |
|
70 | 16 |
|
71 | 17 | Description |
|
0 commit comments