WebKit export of https://bugs.webkit.org/show_bug.cgi?id=238854#37027
Merged
rwlbuis merged 1 commit intoweb-platform-tests:masterfrom Nov 22, 2022
Conversation
mstensho
reviewed
Nov 18, 2022
| @@ -0,0 +1,28 @@ | |||
| <!DOCTYPE html> | |||
| <title>Relative child wider than the column container should not be clipped</title> | |||
Contributor
There was a problem hiding this comment.
Indeed, there should be no clipping here. In fact, I find it somewhat confusing that the topic of clipping is brought up at all. There's nothing in the test that suggests any clipping at all (i.e. no overflow / clip / etc properties).
Maybe this test could be named something like relative-child-overflowing-container?
Contributor
Author
There was a problem hiding this comment.
Fair enough, I think I was confused by the original bug title ("[Multicol] Incorrect clipping when a layer is present between the column and the content layer"). Should be fixed now.
wpt-pr-bot
approved these changes
Nov 21, 2022
Collaborator
wpt-pr-bot
left a comment
wpt-pr-bot
left a comment
There was a problem hiding this comment.
The review process for this patch is being conducted in the WebKit project.
rwlbuis
force-pushed
the
wpt-export-for-webkit-238854
branch
from
0e07f30 to
0923213
Compare
Collaborator
|
This patch has been exported from WebKit; it will be approved automatically once the downstream patch is r+. |
mstensho
approved these changes
Nov 22, 2022
servo-wpt-sync
pushed a commit
to servo/wpt
that referenced
this pull request
Jul 18, 2025
Any CSP violations happening when loading a worker should be reported on the global of the document that creates the worker. Since workers run in different threads, we can't pass in this parent global into the worker global scope. Instead, we need to send a message to the parent event loop to report it on the correct global. Part of web-platform-tests#4577 Fixes web-platform-tests#37027 Signed-off-by: Tim van der Lippe <[email protected]>
servo-wpt-sync
pushed a commit
to servo/wpt
that referenced
this pull request
Jul 18, 2025
Any CSP violations happening when loading a worker should be reported on the global of the document that creates the worker. Since workers run in different threads, we can't pass in this parent global into the worker global scope. Instead, we need to send a message to the parent event loop to report it on the correct global. Part of web-platform-tests#4577 Fixes web-platform-tests#37027 Signed-off-by: Tim van der Lippe <[email protected]>
servo-wpt-sync
pushed a commit
to servo/wpt
that referenced
this pull request
Jul 19, 2025
Any CSP violations happening when loading a worker should be reported on the global of the document that creates the worker. Since workers run in different threads, we can't pass in this parent global into the worker global scope. Instead, we need to send a message to the parent event loop to report it on the correct global. Part of web-platform-tests#4577 Fixes web-platform-tests#37027 Signed-off-by: Tim van der Lippe <[email protected]>
servo-wpt-sync
pushed a commit
to servo/wpt
that referenced
this pull request
Jul 19, 2025
Any CSP violations happening when loading a worker should be reported on the global of the document that creates the worker. Since workers run in different threads, we can't pass in this parent global into the worker global scope. Instead, we need to send a message to the parent event loop to report it on the correct global. Part of web-platform-tests#4577 Fixes web-platform-tests#37027 Signed-off-by: Tim van der Lippe <[email protected]>
servo-wpt-sync
pushed a commit
that referenced
this pull request
Jul 20, 2025
Any CSP violations happening when loading a worker should be reported on the global of the document that creates the worker. Since workers run in different threads, we can't pass in this parent global into the worker global scope. Instead, we need to send a message to the parent event loop to report it on the correct global. Part of #4577 Fixes #37027 Signed-off-by: Tim van der Lippe <[email protected]>
foolip
pushed a commit
that referenced
this pull request
Aug 13, 2025
Any CSP violations happening when loading a worker should be reported on the global of the document that creates the worker. Since workers run in different threads, we can't pass in this parent global into the worker global scope. Instead, we need to send a message to the parent event loop to report it on the correct global. Part of #4577 Fixes #37027 Signed-off-by: Tim van der Lippe <[email protected]>
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
5 participants
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.
No description provided.