Update dependency io.sf.carte:css4j to v5.1 #3842
Open
+1
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
5.0
->5.1
Release Notes
css4j/css4j (io.sf.carte:css4j)
v5.1
Compare Source
January 24, 2025
Highlights
Advanced attr() values
The advanced
attr()
support now follows the current Values Level 5 specification.Although this library has supported the advanced
attr()
value for years now,it was implementing an old version of the specification which is substantially
different to the current one. The new spec is so recent that the old one is
still used by at least one CSS specification (CSS Lists 3) in their sample style
sheet for HTML.
This library should be compatible with the
attr()
which is shipped with theforthcoming Google Chrome 133.
The old
CSSAttrValue
andAttrValue
classes were removed, as the API isincompatible with the new specification that is being implemented by browsers.
More compliant registered custom properties
Also, the handling of registered custom properties is now closer to the Google
Chrome behaviour: registered initial values take precedence over the fallbacks.
Circularity behaviour changed
On the other hand, when
var()
circularities (and other apparent DoS attacks)are found, it is no longer attempted to use the supplied property fallbacks.
It has been found that some websites send content with, for example,
--foo:var(--foo,fallback)
circularities to non-browser user agents, in whatcould be a strategy against web crawlers. Due to the kind of use cases that this
library has, it was determined that it is preferable to just report the
circularity and invalidate the whole value.
If your use case is negatively affected by this decision, please open an issue.
Detail of changes
attr()
support now follows the current Values Level 5specification.
EMPTY
units incountReplaceBy()
.getParameters()
return the sub-values if this is an expressionor a unicode range.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.