-
-
Notifications
You must be signed in to change notification settings - Fork 3.1k
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
layout2020: backdrop filter creates a stacking context #35415
base: main
Are you sure you want to change the base?
layout2020: backdrop filter creates a stacking context #35415
Conversation
41df431
to
3bd1e6a
Compare
🔨 Triggering try run (#13255612864) for Linux (WPT) |
Test results for linux-wpt-layout-2020 from try job (#13255612864): Flaky unexpected result (17)
Stable unexpected results that are known to be intermittent (17)
Stable unexpected results (9)
|
|
The It's just 2 passes so I guess I will just bump stylo to 8af5d515a03bfca5d19fcaa541783327673a951e |
You need to check this.
These changes require tests. Not necessarily new tests, existing tests are fine. But I only see parsing tests among the unexpected results. We need tests for:
|
I can't because I changed the stylo repo to point to my own.
Okay. |
d2c8a56
to
3d25ea2
Compare
What do you mean you can't run You should also rebase (there are conflicts).
Should say "stacking context and a containing block". |
cargo-deny fails with unapproved git forks present in Cargo.lock, and this is part of test-tidy. |
I'll wait to see if and when my PR in servo/stylo#121 lands then just rebase and return it to pointing to the stylo repo's latest tag. I'll force push, so my repo is never actually in the history (i don't think you guys squash and merge). |
Ah, interesting. |
Oh wow, that is so much smarter. I should've done that. |
Hold on, doesn't this defeat the whole purpose of disallowing unapproved forks? Couldn't someone just open a PR with malicious code and then close it, then just point it to the PR? I believe this would bypass that cargo tidy check. |
A malicious person could also edit |
So will you implement |
f658fa4
to
2339cbd
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You need to update test expectations: #35415 (comment)
You need test coverage for establishing a stacking context, and for establishing a containing block for abspos and fixedpos descendants.
I did it! |
Signed-off-by: Josh <[email protected]>
Signed-off-by: Josh <[email protected]>
e8451f4
to
1eb7bd2
Compare
Again: You need test coverage for establishing a stacking context, and for establishing a containing block for abspos and fixedpos descendants. |
Backdrop-filter now creates both a stacking context and a containing block context.
./mach build -d
does not report any errors./mach test-tidy
does not report any errors