[WebMCP] Use HTTPS targets for declarative form tests - #63240
Open
MiguelsPizza wants to merge 1 commit into
Open
MiguelsPizza wants to merge 1 commit into
MiguelsPizza wants to merge 1 commit into
Conversation
Safari shows a native insecure-form confirmation when these HTTPS tests submit to about:blank. The sheet can block WebDriver window cleanup, causing WPT to discard completed subtest results. Use the existing same-origin /common/blank.html resource so submissions remain on HTTPS. Keep iframe targets and all test assertions unchanged.
This branch has not been deployed
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
3 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.
Submitting these HTTPS forms to
about:blankdoesn't work in Safari. We need to change them to a real HTML page so we can use HTTPS. Ran into this while working on the WebMCP polyfill.