зеркало из https://github.com/mozilla/gecko-dev.git
9616df4a8b
Note that it seems unpredictable when we receive the favicon request in the network monitor, for example, on a Linux machine, the favicon request for a static link element after the stylesheet link element in html_cause-test-page.html it happens after the XHR request was received. So instead of using a static link favicon element, we add a favicon link dynamically in tests. Unfortunately there is no handy way to tell a favicon request has done in contents, so we use LinkHandlerParent utility here. Also note that the favicon request is triggered in FaviconLoader.jsm, which means the call stack should NOT be shown (bug 1280266). For now, we intentionally specify the stack and use todo for the case. Differential Revision: https://phabricator.services.mozilla.com/D70572 |
||
|---|---|---|
| .. | ||
| client | ||
| docs | ||
| platform | ||
| server | ||
| shared | ||
| startup | ||
| .eslintrc.js | ||
| .eslintrc.mochitests.js | ||
| .eslintrc.xpcshell.js | ||
| CODE_OF_CONDUCT.md | ||
| moz.build | ||
| templates.mozbuild | ||
| tsconfig.json | ||