Skip to main content

Browse the archive

Revision 9936e8c644dfcfc1c02ba53fa26c501d64eccc11 authored by Yutaka Hirano on 21 November 2017, 10:42:44 UTC, committed by Chromium WPT Sync on 21 November 2017, 10:42:44 UTC 
[XHR] Introduce a mime type parser to a WPT
 
This CL introduces a mime type parser and stringifier to
wpt/XMLHttpRequest/send-content-type-charset in order to accept
implementations that are actually conforming to the spec but were rejected
by the test due to some text representation errors.

Bug: https://github.com/whatwg/mimesniff/issues/39
Change-Id: I99466e2e596bb9c1b7f11267ad4ff0a886913086
1 parent 93f495e
Raw File
format-bom.htm 
<!DOCTYPE html>
<html>
  <head>
    <title>EventSource: BOM</title>
    <script src="/resources/testharness.js"></script>
    <script src="/resources/testharnessreport.js"></script>
  </head>
  <body>
    <div id="log"></div>
    <script>
      var test = async_test(),
          hasbeenone = false,
          hasbeentwo = false
      test.step(function() {
        var source = new EventSource("resources/message.py?message=%EF%BB%BFdata%3A1%0A%0A%EF%BB%BFdata%3A2%0A%0Adata%3A3")
        source.addEventListener("message", listener, false)
      })
      function listener(e) {
        test.step(function() {
          if(e.data == "1")
            hasbeenone = true
          if(e.data == "2")
            hasbeentwo = true
          if(e.data == "3") {
            assert_true(hasbeenone)
            assert_false(hasbeentwo)
            this.close()
            test.done()
          }
        }, this)
      }
    </script>
  </body>
</html>
back to top