Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(139)

Issues Search
    My Issues | Starred     Open | Closed | All

Unified Diff: third_party/WebKit/LayoutTests/imported/web-platform-tests/html/semantics/scripting-1/the-script-element/script-charset-01.html

Issue 1872233002: Remove imported script-charset-01.html and script-charset-02.html. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Created 4 years, 8 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « third_party/WebKit/LayoutTests/W3CImportExpectations ('k') | third_party/WebKit/LayoutTests/imported/web-platform-tests/html/semantics/scripting-1/the-script-element/script-charset-01-expected.txt » ('j') | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: third_party/WebKit/LayoutTests/imported/web-platform-tests/html/semantics/scripting-1/the-script-element/script-charset-01.html
diff --git a/third_party/WebKit/LayoutTests/imported/web-platform-tests/html/semantics/scripting-1/the-script-element/script-charset-01.html b/third_party/WebKit/LayoutTests/imported/web-platform-tests/html/semantics/scripting-1/the-script-element/script-charset-01.html
deleted file mode 100644
index 0b18c7a90c502fc032278e4d30b3d18bc60dcd53..0000000000000000000000000000000000000000
--- a/third_party/WebKit/LayoutTests/imported/web-platform-tests/html/semantics/scripting-1/the-script-element/script-charset-01.html
+++ /dev/null
@@ -1,89 +0,0 @@
-<!DOCTYPE html>
-<head>
- <meta charset="utf-8">
- <title>Script @type: unknown parameters</title>
- <link rel="author" title="askalski" href="github.com/askalski">
- <link rel="help" href="https://html.spec.whatwg.org/multipage/#scriptingLanguages">
- <script src="../../../../../../resources/testharness.js"></script>
- <script src="../../../../../../resources/testharnessreport.js"></script>
- <div id="log"></div>
-
- <!-- "Step1" tests -->
- <!-- charset is set incorrectly via Content Type "text/javascript;charset=utf-8" in response
- which has priority before a correct setting in "charset" attribute of script tag.
- -->
- <script type="text/javascript"
- src="serve-with-content-type.py?fn=external-script-windows1250.js&ct=text/javascript%3Bcharset=utf-8" charset="windows-1250">
- </script>
- <script>
- test(function() {
- //these strings should not match, since the file charset is set incorrectly
- assert_not_equals(window.getSomeString(), "śćążź");
- });
- </script>
- <!-- charset is set correctly via Content Type "text/javascript;charset=utf-8" in response
- which has priority before a incorrect setting in "charset" attribute of script tag.
- -->
-
- <script type="text/javascript"
- src="serve-with-content-type.py?fn=external-script-windows1250.js&ct=text/javascript%3Bcharset=windows-1250" charset="utf-8">
- </script>
- <script>
- //the charset is set correctly via Content Type "text/javascript;charset=windows-1250" in respones
- test(function() {
- assert_equals(window.getSomeString(), "śćążź");
- });
- </script>
-
- <!-- end of step1 tests, now step2 tests -->
- <!-- in this case, the response's Content Type does not bring charset information.
- Second step takes block character encoding if available. -->
- <script type="text/javascript"
- src="serve-with-content-type.py?fn=external-script-windows1250.js&ct=text/javascript" charset="utf-8">
- </script>
- <script>
- test(function() {
- //these strings should not match, since the file charset is set incorrectly in "charset" tag of <script> above
- assert_not_equals(window.getSomeString(), "śćążź");
- });
- </script>
- <!-- charset is set correctly via Content Type "text/javascript;charset=utf-8" in response
- which has priority before a incorrect setting in "charset" attribute of script tag.
- -->
-
- <script type="text/javascript"
- src="serve-with-content-type.py?fn=external-script-windows1250.js&ct=text/javascript" charset="windows-1250">
- </script>
- <script>
- //the charset is set correctly via content attribute in <script> above
- test(function() {
- assert_equals(window.getSomeString(), "śćążź");
- });
- </script>
-
- <!-- end of step2 tests, now step3 tests -->
- <!-- in this case, neither response's Content Type nor charset attribute bring correct charset information.
- Third step takes this document's character encoding (declared correctly as UTF-8). -->
- <script type="text/javascript"
- src="serve-with-content-type.py?fn=external-script-windows1250.js&ct=text/javascript">
- </script>
- <script>
- test(function() {
- //these strings should not match, since the tested file is in windows-1250, and document is utf-8
- assert_not_equals(window.getSomeString(), "śćążź");
- });
- </script>
-
- <script type="text/javascript"
- src="serve-with-content-type.py?fn=external-script-utf8.js&ct=text/javascript">
- </script>
- <script>
- //these strings should match, both document and tested file are utf-8
- test(function() {
- assert_equals(window.getSomeString(), "śćążź");
- });
- </script>
-
- <!-- the last portion of tests (step4) are in file script-charset-02.html
-
-</head>
« no previous file with comments | « third_party/WebKit/LayoutTests/W3CImportExpectations ('k') | third_party/WebKit/LayoutTests/imported/web-platform-tests/html/semantics/scripting-1/the-script-element/script-charset-01-expected.txt » ('j') | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698