Clarify attr() URL limitations and add image-set() example
#41948
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.
Description
This updates the explanation of how
attr()behaves when used in URL-related contexts.The previous text implied a general restriction, but the real limitation applies only when the value is required to be a
<url>type.The revised wording explains that:
attr()values are attr-tainted.<url>(e.g. insideurl()orbackground-image) results in IACVT.image-set()—accept a<string>first, which is later interpreted as a URL. This can allowattr()to work in shorthand properties likebackground, although it does not work inbackground-image.Motivation
This update was made after watching a video by zhangxinxu on bilibili:
https://www.bilibili.com/video/BV1dPkzB3Esx
I realized the documentation should more accurately reflect the difference between
<url>-required contexts and cases where<string>is allowed before URL resolution.