Add test tracking web-exposed CSS properties#42385
Merged
Loirooriol merged 1 commit intoservo:mainfrom Feb 6, 2026
Merged
Conversation
When doing a Stylo upgrade, it may happen that a commit imported from upstream accidentally enables a CSS property on Servo. That is even more likely after https://phabricator.services.mozilla.com/D280900, since the new default is that properties are enabled everywhere. Therefore, this test will help detect these accidents. Ideally, the test would only track CSS properties exposed to stable, but that requires running the test without experimental features, or using internal APIs. So for now, the test will also track experimental properties. Signed-off-by: Oriol Brufau <[email protected]>
|
🔨 Triggering try run (#21736773972) for Linux (WPT) |
jdm
approved these changes
Feb 6, 2026
|
Test results for linux-wpt from try job (#21736773972): Flaky unexpected result (36)
Stable unexpected results that are known to be intermittent (26)
|
|
✨ Try run (#21736773972) succeeded. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
When doing a Stylo upgrade, it may happen that a commit imported from upstream accidentally enables a CSS property on Servo. That is even more likely after https://phabricator.services.mozilla.com/D280900, since the new default is that properties are enabled everywhere.
Therefore, this test will help detect these accidents. Ideally, the test would only track CSS properties exposed to stable, but that requires running the test without experimental features, or using internal APIs. So for now, the test will also track experimental properties.
Testing: just adding a new test, no behavior change