Skip to content
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

REGRESSION(266644@main):[ macOS WK1 ] report-original-url-on-mixed-content-frame.https.sub.html is a constant text failure #28315

Merged
merged 1 commit into from
May 9, 2024

Conversation

brentfulgham
Copy link
Contributor

@brentfulgham brentfulgham commented May 9, 2024

c741b1a

REGRESSION(266644@main):[ macOS WK1 ] report-original-url-on-mixed-content-frame.https.sub.html is a constant text failure
https://bugs.webkit.org/show_bug.cgi?id=266047
<rdar://problem/119349300>

Reviewed by Tim Nguyen.

The original result for  LayoutTests/imported/w3c/web-platform-tests/content-security-policy/reporting/report-original-url-on-mixed-content-frame.https.sub-expected.txt
was failure on all platforms.

Ryan's work in 266644@main progressed this test case in modern WebKit, and he checked that expectation in.

Unfortunately, WebKitLegacy relies on a PingHandle implementation that cannot authenticate against https
(which is a missing feature in the entire deprecated WebKitLegacy platform for the old PingHandle implementation).
We do to intend to invest time working on implementing such a feature in WebKitLegacy, so we expect this
test to fail.

This patch lands a new WebKitLegacy test expectation to document the expected behavior. Note that the console
output on WebKitLegacy shows that the load was blocked properly in WebKitLegacy. It is only the Reporting API
message that fails in this test, simply because WebKitLegacy cannot handle the mixture of an insecure main
page sending reports to an secure reporting target.

* LayoutTests/platform/mac-wk1/TestExpectations:
* LayoutTests/platform/mac-wk1/imported/w3c/web-platform-tests/content-security-policy/reporting/report-original-url-on-mixed-content-frame.https.sub-expected.txt: Added.

Canonical link: https://commits.webkit.org/278543@main

6572a59

Misc iOS, tvOS & watchOS macOS Linux Windows
βœ… πŸ§ͺ style βœ… πŸ›  ios βœ… πŸ›  mac βœ… πŸ›  wpe βœ… πŸ›  wincairo
βœ… πŸ›  ios-sim βœ… πŸ›  mac-AS-debug   πŸ§ͺ wpe-wk2
βœ… πŸ§ͺ webkitperl βœ… πŸ§ͺ ios-wk2 βœ… πŸ§ͺ api-mac βœ… πŸ§ͺ api-wpe
  πŸ§ͺ ios-wk2-wpt βœ… πŸ§ͺ mac-wk1 βœ… πŸ›  wpe-skia
βœ… πŸ§ͺ api-ios βœ… πŸ§ͺ mac-wk2 βœ… πŸ›  gtk
βœ… πŸ›  tv   πŸ§ͺ mac-AS-debug-wk2   πŸ§ͺ gtk-wk2
βœ… πŸ›  tv-sim βœ… πŸ§ͺ mac-wk2-stress   πŸ§ͺ api-gtk
βœ… πŸ›  πŸ§ͺ merge βœ… πŸ›  watch
βœ… πŸ›  watch-sim

@brentfulgham brentfulgham self-assigned this May 9, 2024
@brentfulgham brentfulgham added New Bugs Unclassified bugs are placed in this component until the correct component can be determined. request-merge-queue Request a pull request to be added to merge-queue once ready labels May 9, 2024
@Ahmad-S792 Ahmad-S792 added merge-queue Applied to send a pull request to merge-queue and removed request-merge-queue Request a pull request to be added to merge-queue once ready labels May 9, 2024
…ntent-frame.https.sub.html is a constant text failure

https://bugs.webkit.org/show_bug.cgi?id=266047
<rdar://problem/119349300>

Reviewed by Tim Nguyen.

The original result for  LayoutTests/imported/w3c/web-platform-tests/content-security-policy/reporting/report-original-url-on-mixed-content-frame.https.sub-expected.txt
was failure on all platforms.

Ryan's work in 266644@main progressed this test case in modern WebKit, and he checked that expectation in.

Unfortunately, WebKitLegacy relies on a PingHandle implementation that cannot authenticate against https
(which is a missing feature in the entire deprecated WebKitLegacy platform for the old PingHandle implementation).
We do to intend to invest time working on implementing such a feature in WebKitLegacy, so we expect this
test to fail.

This patch lands a new WebKitLegacy test expectation to document the expected behavior. Note that the console
output on WebKitLegacy shows that the load was blocked properly in WebKitLegacy. It is only the Reporting API
message that fails in this test, simply because WebKitLegacy cannot handle the mixture of an insecure main
page sending reports to an secure reporting target.

* LayoutTests/platform/mac-wk1/TestExpectations:
* LayoutTests/platform/mac-wk1/imported/w3c/web-platform-tests/content-security-policy/reporting/report-original-url-on-mixed-content-frame.https.sub-expected.txt: Added.

Canonical link: https://commits.webkit.org/278543@main
@webkit-commit-queue
Copy link
Collaborator

Committed 278543@main (c741b1a): https://commits.webkit.org/278543@main

Reviewed commits have been landed. Closing PR #28315 and removing active labels.

@webkit-commit-queue webkit-commit-queue merged commit c741b1a into WebKit:main May 9, 2024
@webkit-commit-queue webkit-commit-queue removed the merge-queue Applied to send a pull request to merge-queue label May 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
New Bugs Unclassified bugs are placed in this component until the correct component can be determined.
Projects
None yet
5 participants