Open Bug 1094240 Opened 5 years ago Updated Last year

e10s - disabling the findbar using "disablefastfind" is broken (therefore causes test failures in browser_zbug569342.js)

Categories

(Firefox :: General, defect)

defect
Not set
Points:
2

Tracking

()

Tracking Status
e10s + ---

People

(Reporter: Gijs, Unassigned)

References

(Blocks 1 open bug)

Details

34 INFO TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/general/browser_zbug569342.js | Find bar should not be visible - 
Stack trace:
chrome://mochitests/content/browser/browser/base/content/test/general/browser_zbug569342.js:testFindDisabled/<:65
chrome://mochitests/content/browser/browser/base/content/test/general/browser_zbug569342.js:load/<:23
null:null:0
35 INFO TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/general/browser_zbug569342.js | Find command should be disabled - 
Stack trace:
chrome://mochitests/content/browser/browser/base/content/test/general/browser_zbug569342.js:testFindDisabled/<:66
chrome://mochitests/content/browser/browser/base/content/test/general/browser_zbug569342.js:load/<:23
null:null:0
36 INFO TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/general/browser_zbug569342.js | Find bar should not be visible - 
Stack trace:
chrome://mochitests/content/browser/browser/base/content/test/general/browser_zbug569342.js:testFindDisabled/<:65
chrome://mochitests/content/browser/browser/base/content/test/general/browser_zbug569342.js:load/<:23
null:null:0
37 INFO TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/general/browser_zbug569342.js | Find command should be disabled - 
Stack trace:
chrome://mochitests/content/browser/browser/base/content/test/general/browser_zbug569342.js:testFindDisabled/<:66
chrome://mochitests/content/browser/browser/base/content/test/general/browser_zbug569342.js:load/<:23
null:null:0
38 INFO TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/general/browser_zbug569342.js | Find bar should not be visible - 
Stack trace:
chrome://mochitests/content/browser/browser/base/content/test/general/browser_zbug569342.js:testFindDisabled/<:65
chrome://mochitests/content/browser/browser/base/content/test/general/browser_zbug569342.js:load/<:23
null:null:0
39 INFO TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/general/browser_zbug569342.js | Find command should be disabled - 
Stack trace:
chrome://mochitests/content/browser/browser/base/content/test/general/browser_zbug569342.js:testFindDisabled/<:66
chrome://mochitests/content/browser/browser/base/content/test/general/browser_zbug569342.js:load/<:23
null:null:0
40 INFO TEST-UNEXPECTED-FAIL | chrome://mochitests/content/browser/browser/base/content/test/general/browser_zbug569342.js | Find bar should now be hidden - 
Stack trace:
chrome://mochitests/content/browser/browser/base/content/test/general/browser_zbug569342.js:testFindEnabled/<:83
chrome://mochitests/content/browser/browser/base/content/test/general/browser_zbug569342.js:load/<:23
resource://gre/modules/RemoteAddonsParent.jsm:EventTargetParent.dispatch:485
resource://gre/modules/RemoteAddonsParent.jsm:EventTargetParent.receiveMessage:457
null:null:0
SUITE-END | took 4s
Flags: qe-verify-
Flags: in-testsuite+
Flags: firefox-backlog+
e10s test bugs block e10s, but not a particular milestone.
tracking-e10s: --- → +
Bug 569342 introduced the "disablefastfind" attribute.
MDN says:
"Put disablefastfind="true" on the root element of a XUL document, which is intended to be loaded in a tab, to disable the find bar for the tab with this document. This is used to prevent the find bar from being displayed when it's not supported by the content (such as in the Add-ons manager tab)."

This is used on the following pages:
about:addons, about:permissions, about:config
http://mxr.mozilla.org/mozilla-central/search?string=disablefastfind

I already fixed about:config by making accel+f focus the search box, but the problem is still visible in about:addons (bug 1195060) and about:permissions (bug 661831): You can press accel+f to open the find bar, which should not be possible.
Summary: e10s - fix findbar-related failures in browser_zbug569342.js → e10s - disabling the findbar using "disablefastfind" is broken - causes test failures in browser_zbug569342.js
Bug 967517 claims that this is a regression from 2013-07-07, but I only see this with e10s enabled.
See Also: → 967517
So this was disabled deliberately by bug 862078:

if (!gMultiProcessBrowser ...

} else
  disableFindCommands(false);

http://hg.mozilla.org/mozilla-central/annotate/ba43a48d3c52/browser/base/content/browser.js#l4332
Felipe, do you know who would own this disablefastfind XUL test?
Flags: needinfo?(felipc)
Blake, I see that you touched this test for bug 1055508. This test is disabled for e10s on all desktop platforms. How important is fixing this test?
Flags: needinfo?(felipc)
Duplicate of this bug: 1301959
Note that the code needs fixing here, not the test.
Setting |disablefastfind="true"| has no effect in e10s mode. The code has been explicitly disabled in e10s mode, see comment 4.
Summary: e10s - disabling the findbar using "disablefastfind" is broken - causes test failures in browser_zbug569342.js → e10s - disabling the findbar using "disablefastfind" is broken (therefore causes test failures in browser_zbug569342.js)
Depends on: 1486984
You need to log in before you can comment on or make changes to this bug.