1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
|
"use strict";
const TEST_ROOT =
"http://mochi.test:8888/browser/browser/base/content/test/favicons/";
const TEST_URL = TEST_ROOT + "file_favicon_change_not_in_document.html";
/*
* This test tests a link element won't fire DOMLinkChanged/DOMLinkAdded unless
* it is added to the DOM. See more details in bug 1083895.
*
* Note that there is debounce logic in ContentLinkHandler.jsm, adding a new
* icon link after the icon parsing timeout will trigger a new icon extraction
* cycle. Hence, there should be two favicons loads in this test as it appends
* a new link to the DOM in the timeout callback defined in the test HTML page.
* However, the not-yet-added link element with href as "http://example.org/other-icon"
* should not fire the DOMLinkAdded event, nor should it fire the DOMLinkChanged
* event after its href gets updated later.
*/
add_task(async function () {
let extraTab = (gBrowser.selectedTab = BrowserTestUtils.addTab(
gBrowser,
TEST_ROOT
));
let domLinkAddedFired = 0;
let domLinkChangedFired = 0;
const linkAddedHandler = event => domLinkAddedFired++;
const linkChangedhandler = event => domLinkChangedFired++;
BrowserTestUtils.addContentEventListener(
gBrowser.selectedBrowser,
"DOMLinkAdded",
linkAddedHandler
);
BrowserTestUtils.addContentEventListener(
gBrowser.selectedBrowser,
"DOMLinkChanged",
linkChangedhandler
);
let expectedFavicon = TEST_ROOT + "file_generic_favicon.ico";
let faviconPromise = waitForFavicon(extraTab.linkedBrowser, expectedFavicon);
BrowserTestUtils.loadURIString(extraTab.linkedBrowser, TEST_URL);
await BrowserTestUtils.browserLoaded(extraTab.linkedBrowser);
await faviconPromise;
is(
domLinkAddedFired,
2,
"Should fire the correct number of DOMLinkAdded event."
);
is(domLinkChangedFired, 0, "Should not fire any DOMLinkChanged event.");
gBrowser.removeTab(extraTab);
});
|
