-
-
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
Intermittent failure in /css/cssom-view/MediaQueryList-addListener-handleEvent.html #24571
Labels
I-intermittent
Problem reproduces intermittently.
Comments
This was referenced Apr 13, 2023
This was referenced Apr 27, 2023
3 tasks
This was referenced May 19, 2023
3 tasks
This was referenced Jun 8, 2023
Merged
This was referenced Jun 21, 2023
3 tasks
4 tasks
3 tasks
3 tasks
3 tasks
This was referenced Nov 17, 2023
40 tasks
This was referenced Dec 6, 2024
This was referenced Dec 14, 2024
mrobinson
added a commit
that referenced
this issue
Dec 16, 2024
Post layout, when a `Window` has all of the new `<iframe>` sizes, size any `Window`s for `Pipeline`s in the same `ScriptThread` synchronously. This ensures that when laying out from the outermost frame to the innermost frames, the frames sizes are set properly. There is still an issue where a non-same-`ScriptThread` `<iframe>` sits in between two `<iframe>`s of the same origin. According to the specification these frames should all be synchrnously laid out -- something quite difficult in Servo. This is issue #34655. Fixes #14719. Fixes #24569. Fixes #24571. Fixes #25269. Fixes #25275. Fixes #25285. Fixes #30571. Signed-off-by: Martin Robinson <[email protected]>
mrobinson
added a commit
that referenced
this issue
Dec 16, 2024
…usly Post layout, when a `Window` has all of the new `<iframe>` sizes, size any `Window`s for `Pipeline`s in the same `ScriptThread` synchronously. This ensures that when laying out from the outermost frame to the innermost frames, the frames sizes are set properly. There is still an issue where a non-same-`ScriptThread` `<iframe>` sits in between two `<iframe>`s of the same origin. According to the specification these frames should all be synchrnously laid out -- something quite difficult in Servo. This is issue #34655. Fixes #14719. Fixes #24569. Fixes #24571. Fixes #25269. Fixes #25275. Fixes #25285. Fixes #30571. Signed-off-by: Martin Robinson <[email protected]>
mrobinson
added a commit
to mrobinson/servo
that referenced
this issue
Dec 16, 2024
…usly Post layout, when a `Window` has all of the new `<iframe>` sizes, size any `Window`s for `Pipeline`s in the same `ScriptThread` synchronously. This ensures that when laying out from the outermost frame to the innermost frames, the frames sizes are set properly. There is still an issue where a non-same-`ScriptThread` `<iframe>` sits in between two `<iframe>`s of the same origin. According to the specification these frames should all be synchrnously laid out -- something quite difficult in Servo. This is issue servo#34655. This is the first change in a series of changes to improve the consistency of `<iframe>` loading and sizing. Fixes servo#14719. Fixes servo#24569. Fixes servo#24571. Fixes servo#25269. Fixes servo#25275. Fixes servo#25285. Fixes servo#30571. Signed-off-by: Martin Robinson <[email protected]>
3 tasks
mrobinson
added a commit
to mrobinson/servo
that referenced
this issue
Dec 17, 2024
…usly Post layout, when a `Window` has all of the new `<iframe>` sizes, size any `Window`s for `Pipeline`s in the same `ScriptThread` synchronously. This ensures that when laying out from the outermost frame to the innermost frames, the frames sizes are set properly. There is still an issue where a non-same-`ScriptThread` `<iframe>` sits in between two `<iframe>`s of the same origin. According to the specification these frames should all be synchrnously laid out -- something quite difficult in Servo. This is issue servo#34655. This is the first change in a series of changes to improve the consistency of `<iframe>` loading and sizing. Fixes servo#14719. Fixes servo#24569. Fixes servo#24571. Fixes servo#25269. Fixes servo#25275. Fixes servo#25285. Fixes servo#30571. Signed-off-by: Martin Robinson <[email protected]>
mrobinson
added a commit
to mrobinson/servo
that referenced
this issue
Dec 17, 2024
…usly Post layout, when a `Window` has all of the new `<iframe>` sizes, size any `Window`s for `Pipeline`s in the same `ScriptThread` synchronously. This ensures that when laying out from the outermost frame to the innermost frames, the frames sizes are set properly. There is still an issue where a non-same-`ScriptThread` `<iframe>` sits in between two `<iframe>`s of the same origin. According to the specification these frames should all be synchrnously laid out -- something quite difficult in Servo. This is issue servo#34655. This is the first change in a series of changes to improve the consistency of `<iframe>` loading and sizing. Fixes servo#14719. Fixes servo#24569. Fixes servo#24571. Fixes servo#25269. Fixes servo#25275. Fixes servo#25285. Fixes servo#30571. Signed-off-by: Martin Robinson <[email protected]>
github-merge-queue bot
pushed a commit
that referenced
this issue
Dec 17, 2024
…usly (#34656) Post layout, when a `Window` has all of the new `<iframe>` sizes, size any `Window`s for `Pipeline`s in the same `ScriptThread` synchronously. This ensures that when laying out from the outermost frame to the innermost frames, the frames sizes are set properly. There is still an issue where a non-same-`ScriptThread` `<iframe>` sits in between two `<iframe>`s of the same origin. According to the specification these frames should all be synchrnously laid out -- something quite difficult in Servo. This is issue #34655. This is the first change in a series of changes to improve the consistency of `<iframe>` loading and sizing. Fixes #14719. Fixes #24569. Fixes #24571. Fixes #25269. Fixes #25275. Fixes #25285. Fixes #30571. Signed-off-by: Martin Robinson <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The text was updated successfully, but these errors were encountered: