-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
HTML: split out navigation tests for URL query-encoding tests #11300
Conversation
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.
Thanks for doing this! I have some style nits, but I'm never quite sure whether we should enforce those or not.
Will you file bugs against browsers too for stuff they fail? (Although maybe that's redundant with the bugs I filed already... Hmm.)
Happy to file bugs |
Safari passes. |
The `poll_for_stash` function was relocated from `resolve-url.js` in service of a test refactoring [1]. However, the following tests depend on the presence of that function in that file: - html/infrastructure/urls/resolving-urls/query-encoding/utf-8.html - html/infrastructure/urls/resolving-urls/query-encoding/windows-1251.html - html/infrastructure/urls/resolving-urls/query-encoding/windows-1252.html Restore the function to its original location and persist the copy. [1] web-platform-tests#11300
When the query encoding navigation tests were refactored to use WPT's "variant" feature [1], the new structure omitted one of the encodings which was previously tested. Although the encoding will be used when a variant is not specified, the automation tooling only uses variants which are explicitly specified. This can be observed through the `--list-tests` flag of the `wpt run` command: $ ./wpt run --list-tests firefox html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html /html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=utf8 /html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=x-cp1251 Explicitly declare the default variant, restoring the original test coverage. [1] #11300
When the query encoding navigation tests were refactored to use WPT's "variant" feature [1], the new structure omitted one of the encodings which was previously tested. Although the encoding will be used when a variant is not specified, the automation tooling only uses variants which are explicitly specified. This can be observed through the `--list-tests` flag of the `wpt run` command: $ ./wpt run --list-tests firefox html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html /html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=utf8 /html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=x-cp1251 Explicitly declare the default variant, restoring the original test coverage. [1] web-platform-tests#11300
The `poll_for_stash` function was relocated from `resolve-url.js` in service of a test refactoring [1]. However, the following tests depend on the presence of that function in that file: - html/infrastructure/urls/resolving-urls/query-encoding/utf-8.html - html/infrastructure/urls/resolving-urls/query-encoding/windows-1251.html - html/infrastructure/urls/resolving-urls/query-encoding/windows-1252.html Restore the function to its original location and persist the copy. [1] #11300
When the query encoding navigation tests were refactored to use WPT's "variant" feature [1], the new structure omitted one of the encodings which was previously tested. Although the encoding will be used when a variant is not specified, the automation tooling only uses variants which are explicitly specified. This can be observed through the `--list-tests` flag of the `wpt run` command: $ ./wpt run --list-tests firefox html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html /html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=utf8 /html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=x-cp1251 Explicitly declare the default variant, restoring the original test coverage. [1] #11300
…encoding, a=testonly Automatic update from web-platform-tests [html] Restore utility method for query encoding The `poll_for_stash` function was relocated from `resolve-url.js` in service of a test refactoring [1]. However, the following tests depend on the presence of that function in that file: - html/infrastructure/urls/resolving-urls/query-encoding/utf-8.html - html/infrastructure/urls/resolving-urls/query-encoding/windows-1251.html - html/infrastructure/urls/resolving-urls/query-encoding/windows-1252.html Restore the function to its original location and persist the copy. [1] web-platform-tests/wpt#11300 -- wpt-commits: 9830c5ab1191c788adf006023da46aea07da46f8 wpt-pr: 15255
…ng, a=testonly Automatic update from web-platform-tests HTML: restore coverage for query encoding When the query encoding navigation tests were refactored to use WPT's "variant" feature [1], the new structure omitted one of the encodings which was previously tested. Although the encoding will be used when a variant is not specified, the automation tooling only uses variants which are explicitly specified. This can be observed through the `--list-tests` flag of the `wpt run` command: $ ./wpt run --list-tests firefox html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html /html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=utf8 /html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=x-cp1251 Explicitly declare the default variant, restoring the original test coverage. [1] web-platform-tests/wpt#11300 -- wpt-commits: 0b594535b4d94217964a40288e3f535c452bb8f3 wpt-pr: 15256
…encoding, a=testonly Automatic update from web-platform-tests [html] Restore utility method for query encoding The `poll_for_stash` function was relocated from `resolve-url.js` in service of a test refactoring [1]. However, the following tests depend on the presence of that function in that file: - html/infrastructure/urls/resolving-urls/query-encoding/utf-8.html - html/infrastructure/urls/resolving-urls/query-encoding/windows-1251.html - html/infrastructure/urls/resolving-urls/query-encoding/windows-1252.html Restore the function to its original location and persist the copy. [1] web-platform-tests/wpt#11300 -- wpt-commits: 9830c5ab1191c788adf006023da46aea07da46f8 wpt-pr: 15255
…ng, a=testonly Automatic update from web-platform-tests HTML: restore coverage for query encoding When the query encoding navigation tests were refactored to use WPT's "variant" feature [1], the new structure omitted one of the encodings which was previously tested. Although the encoding will be used when a variant is not specified, the automation tooling only uses variants which are explicitly specified. This can be observed through the `--list-tests` flag of the `wpt run` command: $ ./wpt run --list-tests firefox html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html /html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=utf8 /html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=x-cp1251 Explicitly declare the default variant, restoring the original test coverage. [1] web-platform-tests/wpt#11300 -- wpt-commits: 0b594535b4d94217964a40288e3f535c452bb8f3 wpt-pr: 15256
…encoding, a=testonly Automatic update from web-platform-tests [html] Restore utility method for query encoding The `poll_for_stash` function was relocated from `resolve-url.js` in service of a test refactoring [1]. However, the following tests depend on the presence of that function in that file: - html/infrastructure/urls/resolving-urls/query-encoding/utf-8.html - html/infrastructure/urls/resolving-urls/query-encoding/windows-1251.html - html/infrastructure/urls/resolving-urls/query-encoding/windows-1252.html Restore the function to its original location and persist the copy. [1] web-platform-tests/wpt#11300 -- wpt-commits: 9830c5ab1191c788adf006023da46aea07da46f8 wpt-pr: 15255
…ng, a=testonly Automatic update from web-platform-tests HTML: restore coverage for query encoding When the query encoding navigation tests were refactored to use WPT's "variant" feature [1], the new structure omitted one of the encodings which was previously tested. Although the encoding will be used when a variant is not specified, the automation tooling only uses variants which are explicitly specified. This can be observed through the `--list-tests` flag of the `wpt run` command: $ ./wpt run --list-tests firefox html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html /html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=utf8 /html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=x-cp1251 Explicitly declare the default variant, restoring the original test coverage. [1] web-platform-tests/wpt#11300 -- wpt-commits: 0b594535b4d94217964a40288e3f535c452bb8f3 wpt-pr: 15256
…encoding, a=testonly Automatic update from web-platform-tests [html] Restore utility method for query encoding The `poll_for_stash` function was relocated from `resolve-url.js` in service of a test refactoring [1]. However, the following tests depend on the presence of that function in that file: - html/infrastructure/urls/resolving-urls/query-encoding/utf-8.html - html/infrastructure/urls/resolving-urls/query-encoding/windows-1251.html - html/infrastructure/urls/resolving-urls/query-encoding/windows-1252.html Restore the function to its original location and persist the copy. [1] web-platform-tests/wpt#11300 -- wpt-commits: 9830c5ab1191c788adf006023da46aea07da46f8 wpt-pr: 15255
…ng, a=testonly Automatic update from web-platform-tests HTML: restore coverage for query encoding When the query encoding navigation tests were refactored to use WPT's "variant" feature [1], the new structure omitted one of the encodings which was previously tested. Although the encoding will be used when a variant is not specified, the automation tooling only uses variants which are explicitly specified. This can be observed through the `--list-tests` flag of the `wpt run` command: $ ./wpt run --list-tests firefox html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html /html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=utf8 /html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=x-cp1251 Explicitly declare the default variant, restoring the original test coverage. [1] web-platform-tests/wpt#11300 -- wpt-commits: 0b594535b4d94217964a40288e3f535c452bb8f3 wpt-pr: 15256
…encoding, a=testonly Automatic update from web-platform-tests [html] Restore utility method for query encoding The `poll_for_stash` function was relocated from `resolve-url.js` in service of a test refactoring [1]. However, the following tests depend on the presence of that function in that file: - html/infrastructure/urls/resolving-urls/query-encoding/utf-8.html - html/infrastructure/urls/resolving-urls/query-encoding/windows-1251.html - html/infrastructure/urls/resolving-urls/query-encoding/windows-1252.html Restore the function to its original location and persist the copy. [1] web-platform-tests/wpt#11300 -- wpt-commits: 9830c5ab1191c788adf006023da46aea07da46f8 wpt-pr: 15255 UltraBlame original commit: d2ff85c428aa2bddcf4dc71904e311ffa22edaf0
…ng, a=testonly Automatic update from web-platform-tests HTML: restore coverage for query encoding When the query encoding navigation tests were refactored to use WPT's "variant" feature [1], the new structure omitted one of the encodings which was previously tested. Although the encoding will be used when a variant is not specified, the automation tooling only uses variants which are explicitly specified. This can be observed through the `--list-tests` flag of the `wpt run` command: $ ./wpt run --list-tests firefox html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html /html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=utf8 /html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=x-cp1251 Explicitly declare the default variant, restoring the original test coverage. [1] web-platform-tests/wpt#11300 -- wpt-commits: 0b594535b4d94217964a40288e3f535c452bb8f3 wpt-pr: 15256 UltraBlame original commit: 9b419751710b3922d924ca5400071d90a24a1139
…encoding, a=testonly Automatic update from web-platform-tests [html] Restore utility method for query encoding The `poll_for_stash` function was relocated from `resolve-url.js` in service of a test refactoring [1]. However, the following tests depend on the presence of that function in that file: - html/infrastructure/urls/resolving-urls/query-encoding/utf-8.html - html/infrastructure/urls/resolving-urls/query-encoding/windows-1251.html - html/infrastructure/urls/resolving-urls/query-encoding/windows-1252.html Restore the function to its original location and persist the copy. [1] web-platform-tests/wpt#11300 -- wpt-commits: 9830c5ab1191c788adf006023da46aea07da46f8 wpt-pr: 15255 UltraBlame original commit: d2ff85c428aa2bddcf4dc71904e311ffa22edaf0
…ng, a=testonly Automatic update from web-platform-tests HTML: restore coverage for query encoding When the query encoding navigation tests were refactored to use WPT's "variant" feature [1], the new structure omitted one of the encodings which was previously tested. Although the encoding will be used when a variant is not specified, the automation tooling only uses variants which are explicitly specified. This can be observed through the `--list-tests` flag of the `wpt run` command: $ ./wpt run --list-tests firefox html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html /html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=utf8 /html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=x-cp1251 Explicitly declare the default variant, restoring the original test coverage. [1] web-platform-tests/wpt#11300 -- wpt-commits: 0b594535b4d94217964a40288e3f535c452bb8f3 wpt-pr: 15256 UltraBlame original commit: 9b419751710b3922d924ca5400071d90a24a1139
…encoding, a=testonly Automatic update from web-platform-tests [html] Restore utility method for query encoding The `poll_for_stash` function was relocated from `resolve-url.js` in service of a test refactoring [1]. However, the following tests depend on the presence of that function in that file: - html/infrastructure/urls/resolving-urls/query-encoding/utf-8.html - html/infrastructure/urls/resolving-urls/query-encoding/windows-1251.html - html/infrastructure/urls/resolving-urls/query-encoding/windows-1252.html Restore the function to its original location and persist the copy. [1] web-platform-tests/wpt#11300 -- wpt-commits: 9830c5ab1191c788adf006023da46aea07da46f8 wpt-pr: 15255 UltraBlame original commit: 2384c1c7af5a385461ca25c280aadaed4e46d3ad
…ng, a=testonly Automatic update from web-platform-tests HTML: restore coverage for query encoding When the query encoding navigation tests were refactored to use WPT's "variant" feature [1], the new structure omitted one of the encodings which was previously tested. Although the encoding will be used when a variant is not specified, the automation tooling only uses variants which are explicitly specified. This can be observed through the `--list-tests` flag of the `wpt run` command: $ ./wpt run --list-tests firefox html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html /html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=utf8 /html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=x-cp1251 Explicitly declare the default variant, restoring the original test coverage. [1] web-platform-tests/wpt#11300 -- wpt-commits: 0b594535b4d94217964a40288e3f535c452bb8f3 wpt-pr: 15256 UltraBlame original commit: 53e0aa99149f34d0facaa1571ff088c36d1714c7
…encoding, a=testonly Automatic update from web-platform-tests [html] Restore utility method for query encoding The `poll_for_stash` function was relocated from `resolve-url.js` in service of a test refactoring [1]. However, the following tests depend on the presence of that function in that file: - html/infrastructure/urls/resolving-urls/query-encoding/utf-8.html - html/infrastructure/urls/resolving-urls/query-encoding/windows-1251.html - html/infrastructure/urls/resolving-urls/query-encoding/windows-1252.html Restore the function to its original location and persist the copy. [1] web-platform-tests/wpt#11300 -- wpt-commits: 9830c5ab1191c788adf006023da46aea07da46f8 wpt-pr: 15255 UltraBlame original commit: d2ff85c428aa2bddcf4dc71904e311ffa22edaf0
…ng, a=testonly Automatic update from web-platform-tests HTML: restore coverage for query encoding When the query encoding navigation tests were refactored to use WPT's "variant" feature [1], the new structure omitted one of the encodings which was previously tested. Although the encoding will be used when a variant is not specified, the automation tooling only uses variants which are explicitly specified. This can be observed through the `--list-tests` flag of the `wpt run` command: $ ./wpt run --list-tests firefox html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html /html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=utf8 /html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=x-cp1251 Explicitly declare the default variant, restoring the original test coverage. [1] web-platform-tests/wpt#11300 -- wpt-commits: 0b594535b4d94217964a40288e3f535c452bb8f3 wpt-pr: 15256 UltraBlame original commit: 9b419751710b3922d924ca5400071d90a24a1139
…encoding, a=testonly Automatic update from web-platform-tests [html] Restore utility method for query encoding The `poll_for_stash` function was relocated from `resolve-url.js` in service of a test refactoring [1]. However, the following tests depend on the presence of that function in that file: - html/infrastructure/urls/resolving-urls/query-encoding/utf-8.html - html/infrastructure/urls/resolving-urls/query-encoding/windows-1251.html - html/infrastructure/urls/resolving-urls/query-encoding/windows-1252.html Restore the function to its original location and persist the copy. [1] web-platform-tests/wpt#11300 -- wpt-commits: 9830c5ab1191c788adf006023da46aea07da46f8 wpt-pr: 15255 UltraBlame original commit: 2384c1c7af5a385461ca25c280aadaed4e46d3ad
…ng, a=testonly Automatic update from web-platform-tests HTML: restore coverage for query encoding When the query encoding navigation tests were refactored to use WPT's "variant" feature [1], the new structure omitted one of the encodings which was previously tested. Although the encoding will be used when a variant is not specified, the automation tooling only uses variants which are explicitly specified. This can be observed through the `--list-tests` flag of the `wpt run` command: $ ./wpt run --list-tests firefox html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html /html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=utf8 /html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=x-cp1251 Explicitly declare the default variant, restoring the original test coverage. [1] web-platform-tests/wpt#11300 -- wpt-commits: 0b594535b4d94217964a40288e3f535c452bb8f3 wpt-pr: 15256 UltraBlame original commit: 53e0aa99149f34d0facaa1571ff088c36d1714c7
…encoding, a=testonly Automatic update from web-platform-tests [html] Restore utility method for query encoding The `poll_for_stash` function was relocated from `resolve-url.js` in service of a test refactoring [1]. However, the following tests depend on the presence of that function in that file: - html/infrastructure/urls/resolving-urls/query-encoding/utf-8.html - html/infrastructure/urls/resolving-urls/query-encoding/windows-1251.html - html/infrastructure/urls/resolving-urls/query-encoding/windows-1252.html Restore the function to its original location and persist the copy. [1] web-platform-tests/wpt#11300 -- wpt-commits: 9830c5ab1191c788adf006023da46aea07da46f8 wpt-pr: 15255 UltraBlame original commit: 2384c1c7af5a385461ca25c280aadaed4e46d3ad
…ng, a=testonly Automatic update from web-platform-tests HTML: restore coverage for query encoding When the query encoding navigation tests were refactored to use WPT's "variant" feature [1], the new structure omitted one of the encodings which was previously tested. Although the encoding will be used when a variant is not specified, the automation tooling only uses variants which are explicitly specified. This can be observed through the `--list-tests` flag of the `wpt run` command: $ ./wpt run --list-tests firefox html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html /html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=utf8 /html/infrastructure/urls/resolving-urls/query-encoding/navigation.sub.html?encoding=x-cp1251 Explicitly declare the default variant, restoring the original test coverage. [1] web-platform-tests/wpt#11300 -- wpt-commits: 0b594535b4d94217964a40288e3f535c452bb8f3 wpt-pr: 15256 UltraBlame original commit: 53e0aa99149f34d0facaa1571ff088c36d1714c7
Part of #11269 and #4934.
The new test still times out because
ping
is not supported, but passes in Firefox withsend_pings
pref enabled.