Commit 5e20c14b authored by Daniel Varga's avatar Daniel Varga
Browse files

Backed out 2 changesets (bug 1322385) for mochitest failure at:...

Backed out 2 changesets (bug 1322385) for mochitest failure at: toolkit/content/tests/chrome/test_findbar_entireword.xul

Backed out changeset 31a0bd977b2f (bug 1322385)
Backed out changeset feef45c56170 (bug 1322385)
parent 02861106
Loading
Loading
Loading
Loading
+0 −2
Original line number Diff line number Diff line
@@ -73,8 +73,6 @@ skip-if = os == "linux" || os == "mac" # Bug 1498336
[browser_touch_device.js]
[browser_touch_does_not_trigger_hover_states.js]
[browser_touch_simulation.js]
[browser_typeahead_find.js]
fail-if = true # Bug 1547783
[browser_user_agent_input.js]
[browser_viewport_basics.js]
[browser_viewport_resizing_fixed_width.js]
+0 −75
Original line number Diff line number Diff line
/* This Source Code Form is subject to the terms of the Mozilla Public
 * License, v. 2.0. If a copy of the MPL was not distributed with this
 * file, You can obtain one at http://mozilla.org/MPL/2.0/. */

"use strict";

/**
 * This test attempts to exercise automatic triggering of typeaheadfind
 * within RDM content. It does this by simulating keystrokes while
 * various elements in the RDM content are focused.

 * The test currently does not work due to two reasons:
 * 1) The simulated key events do not behave the same as real key events.
 *    Specifically, when this test is run on an un-patched build, it
 *    fails to trigger typeaheadfind when the input element is focused.
 * 2) In order to test that typeahead find has or has not occurred, this
 *    test checks the values held by the findBar associated with the
 *    tab that contains the RDM pane. That findBar has no values, though
 *    they appear correctly when the steps are run interactively. This
 *    indicates that some other findBar is receiving the typeaheadfind
 *    characters.
 */

const TEST_URL = "data:text/html;charset=utf-8," +
  "<body id=\"body\"><input id=\"input\" type=\"text\"/><p>text</body>";

addRDMTask(TEST_URL, async function({ ui, manager }) {
  // Turn on the pref that allows meta viewport support.
  await pushPref("accessibility.typeaheadfind", true);

  const store = ui.toolWindow.store;

  // Wait until the viewport has been added.
  await waitUntilState(store, state => state.viewports.length == 1);

  const browser = ui.getViewportBrowser();

  info("--- Starting test output ---");

  const expected = [
    {
      id: "body",
      findTriggered: true,
    },
    {
      id: "input",
      findTriggered: false,
    },
  ];

  for (const e of expected) {
    await ContentTask.spawn(browser, { e }, async function(args) {
      const { e: values } = args;
      const element = content.document.getElementById(values.id);

      // Set focus on the desired element.
      element.focus();
    });

    // Press the 'T' key and see if find is triggered.
    await BrowserTestUtils.synthesizeKey("t", {}, browser);

    const findBar = await gBrowser.getFindBar();

    const findIsTriggered = (findBar._findField.value == "t");
    is(findIsTriggered, e.findTriggered, "Text input with focused element " + e.id +
      " should " + (e.findTriggered ? "" : "not ") + "trigger find.");
    findBar._findField.value = "";

    await ContentTask.spawn(browser, {}, async function() {
      // Clear focus.
      content.document.activeElement.blur();
    });
  }
});
+0 −1
Original line number Diff line number Diff line
@@ -170,7 +170,6 @@ let ACTORS = {
  FindBar: {
    child: {
      module: "resource://gre/actors/FindBarChild.jsm",
      allFrames: true,
      events: {
        "keypress": {mozSystemGroup: true},
      },
+0 −1
Original line number Diff line number Diff line
@@ -303,7 +303,6 @@ var BrowserUtils = {
      if (elt instanceof win.HTMLTextAreaElement ||
          elt instanceof win.HTMLSelectElement ||
          elt instanceof win.HTMLObjectElement ||
          elt instanceof win.HTMLIFrameElement ||
          elt instanceof win.HTMLEmbedElement)
        return false;
    }