author Edgar Chen <>
Wed, 10 Oct 2018 20:34:44 +0000
changeset 488974 01894c0196cb83376acc4bfce32f9d4a176d3b4e
parent 488598 ecce651fad51ab1a5718b6e6f208093ec075612d
permissions -rw-r--r--
Bug 1497554 - Split new test into test_group_touchevents-4.html; r=kats Differential Revision:

  <meta charset="utf-8">
  <title>Various touch tests that spawn in new windows (3)</title>
  <script type="application/javascript" src="/tests/SimpleTest/SimpleTest.js"></script>
  <script type="application/javascript" src="apz_test_native_event_utils.js"></script>
  <script type="application/javascript" src="apz_test_utils.js"></script>
  <link rel="stylesheet" type="text/css" href="/tests/SimpleTest/test.css"/>
  <script type="application/javascript">

var touch_action_prefs = [
  ["layout.css.touch_action.enabled", true],
  ["apz.test.fails_with_native_injection", getPlatform() == "windows"],

var subtests = [
  // Simple test to exercise touch-action CSS property
  {'file': 'helper_touch_action.html', 'prefs': touch_action_prefs},
  // More complex touch-action tests, with overlapping regions and such
  {'file': 'helper_touch_action_complex.html', 'prefs': touch_action_prefs},
  // Tests that touch-action CSS properties are handled in APZ without waiting
  // on the main-thread, when possible
  {'file': 'helper_touch_action_regions.html', 'prefs': touch_action_prefs},

  // Add new subtests to test_group_touch_events-4.html, not this file.

if (isApzEnabled()) {
  ok(window.TouchEvent, "Check if TouchEvent is supported (it should be, the test harness forces it on everywhere)");
  if (getPlatform() == "android") {
    // This has a lot of subtests, and Android emulators are slow.

  window.onload = function() {
    .then(SimpleTest.finish, SimpleTest.finish);