Use new ChromeUtils.getXPCOMErrorName() method to get platform error names
Categories
(DevTools :: Netmonitor, task)
Tracking
(firefox97 fixed)
| Tracking | Status | |
|---|---|---|
| firefox97 | --- | fixed |
People
(Reporter: ochameau, Assigned: ochameau)
References
(Blocks 1 open bug)
Details
Attachments
(3 files)
Bug 1740543 added a new method to retrieve the name of errors as a string of any given XPCOM error code.
Meaning we could get rid of this outdated copy of c++ code we were using over there:
https://searchfox.org/mozilla-central/rev/71befbc9bc348d33f0c7307dc48e3cb36ba78650/devtools/server/actors/network-monitor/utils/network-utils.js#31-551
| Assignee | ||
Comment 1•3 years ago
|
||
| Assignee | ||
Comment 2•3 years ago
|
||
In this test, there is two that are actually dedicated to cover ResourceCommand internal cache
and the precise behavior of ignoreExistingResources: true/false.
I pulled them off in a dedicated test file and tried to simplified them a bit.
Because the server doesn't really support fetch request done before calling watchResources,
this test is a bit hard to understand. So I tried to make it clear via extensive comments.
Then, my goal is to reuse the third and simplier test to extend the coverage of NETWORK_EVENT
with many other assertions.
| Assignee | ||
Comment 3•3 years ago
|
||
| Assignee | ||
Comment 4•3 years ago
|
||
Comment 6•3 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/0f4c55b3bea7
https://hg.mozilla.org/mozilla-central/rev/10b6a5257630
https://hg.mozilla.org/mozilla-central/rev/f73088ff3b94
Description
•