New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
selectors: Revert as many changes from upstream as possible #31365
Conversation
🔨 Triggering try run (#7928855850) for Linux WPT layout-2020 |
Test results for linux-wpt-layout-2020 from try job (#7928855850): Flaky unexpected result (8)
Stable unexpected results that are known to be intermittent (17)
Stable unexpected results (10)
|
|
🔨 Triggering try run (#7929516395) for Linux WPT layout-2020 |
(retrying due to #31364) |
79ccae4
to
24e403f
Compare
I think we'll need to keep the changes from 29f6170 judging by the test results. I've added those back. |
🔨 Triggering try run (#7929692406) for Linux WPT layout-2020 |
Test results for linux-wpt-layout-2020 from try job (#7929692406): Flaky unexpected result (12)
Stable unexpected results that are known to be intermittent (19)
Stable unexpected results (1)
|
I think this is ready for review. The one failure is due to the new test expectation that has now landed in main. |
|
This is part of the preparation for splitting stylo into a separate crate. We have made various changes to selectors includings: 1. Bumping the rust edition 2. Fixing typos and updating links In addition to reverting those changes, this PR pulls in some changes to selectors we seem to have missed in the process of updates.
24e403f
to
80ced39
Compare
🔨 Triggering try run (#7940775404) for Linux WPT |
Test results for linux-wpt-layout-2020 from try job (#7940775404): Flaky unexpected result (17)
Stable unexpected results that are known to be intermittent (20)
|
✨ Try run (#7940775404) succeeded. |
Are the plans to re-apply (any of) these changes upstream? |
We're trying to only revert changes that don't make sense to push upstream. In this case most of the changes are due to rust edition updates that are better managed according to the needs of Gecko. The rest we hope to upstream once we fully sync. |
This builds successfully with: $ cargo build --features servo (as of servo#31351, 31363, 31358, 31365) This patch is up to date as of: * servo/servo#31351 * servo/servo#31363 * servo/servo#31358 * servo/servo#31365 * servo/servo#31387 * servo/servo#31408
This builds successfully with: $ cargo build --features servo (as of servo#31351, 31363, 31358, 31365) This patch is up to date as of: * servo/servo#31351 * servo/servo#31363 * servo/servo#31358 * servo/servo#31365 * servo/servo#31387 * servo/servo#31408
This builds successfully with: $ cargo build --features servo (as of servo#31351, 31363, 31358, 31365) This patch is up to date as of: * servo/servo#31351 * servo/servo#31363 * servo/servo#31358 * servo/servo#31365 * servo/servo#31387 * servo/servo#31408
This builds successfully with: $ cargo build --features servo (as of servo#31351, 31363, 31358, 31365) This patch is up to date as of: * servo/servo#31351 * servo/servo#31363 * servo/servo#31358 * servo/servo#31365 * servo/servo#31387 * servo/servo#31408
This builds successfully with: $ cargo build --features servo (as of servo#31351, 31363, 31358, 31365) This patch is up to date as of: * servo/servo#31351 * servo/servo#31363 * servo/servo#31358 * servo/servo#31365 * servo/servo#31387 * servo/servo#31408
This is part of the preparation for splitting stylo into a separate
crate. We have made various changes to selectors includings:
In addition to reverting those changes, this PR pulls in some changes to
selectors we seem to have missed in the process of updates.
./mach build -d
does not report any errors./mach test-tidy
does not report any errors