khronosschoty
/
palemoon-dev


			
				
					
						
						
							12345678910111213141516171819202122232425262728293031323334353637383940
							<!DOCTYPE HTML>
<html>
<!--
https://bugzilla.mozilla.org/show_bug.cgi?id=1000870
-->
  <head>
    <meta charset="utf-8">
    <title>Test for Bug 1000870</title>
    <meta name="author" content="Maksim Lebedev" />
    <script type="text/javascript" src="/tests/SimpleTest/SimpleTest.js"></script>
    <script type="text/javascript" src="/tests/SimpleTest/EventUtils.js"></script>
    <script type="text/javascript" src="mochitest_support_external.js"></script>
    <link rel="stylesheet" type="text/css" href="/tests/SimpleTest/test.css"/>
    <script type="text/javascript">
      SimpleTest.waitForExplicitFinish();
      function startTest() {
        runTestInNewWindow("pointerevent_change-touch-action-onpointerdown_touch-manual.html");
      }
      function executeTest(int_win) {
        const WM_VSCROLL = 0x0115;
        sendTouchEvent(int_win, "target0", "touchstart");
        sendTouchEvent(int_win, "target0", "touchmove");
        sendTouchEvent(int_win, "target0", "touchend");

        // NOTE: This testcase is about that modifying touch-action during a
        // pointerdown callback "should not" affect the gesture detection of the
        // touch session started by the pointerdown. That is, a scroll should
        // still fired by gesture detection, instead of launching by our own.
        var utils = _getDOMWindowUtils(int_win);
        var target0 = int_win.document.getElementById("target0");
        utils.sendNativeMouseScrollEvent(target0.getBoundingClientRect().left + 5,
                                        target0.getBoundingClientRect().top + 5,
                                        WM_VSCROLL, 10, 10, 0, 0, 0, target0);
      }
    </script>
  </head>
  <body>
  </body>
</html>