1461633 - Implement devtools.inspectedWindow.onResourceContentCommitted

Status: NEW

(WebExtensions :: Developer Tools, enhancement, P3)

Description

[Razvan Caliman [:rcaliman]]

devtools.inspectedWindow.onResourceContentCommitted is not yet implemented according to MDN: https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Extending_the_developer_tools#Limitations_of_the_devtools_APIs

This API endpoint is necessary for extensions that track changes to assets with the purpose of creating diffs or exporting changes.

One such extension that uses this is DevTools Autosave for Chrome:
https://chrome.google.com/webstore/detail/devtools-autosave/mlejngncgiocofkcbnnpaieapabmanfl?hl=en

Without this endpoint, it is impractical (if not impossible) to port such extensions to work on Firefox.

Comment 1

[Luca Greco [:rpl] [:luca] [:lgreco]]

Currently every one of the integrated developer tools is doing its own work to list and track the "resources" part of the developer tools target, while these devtools APIs (getResources, onResourceAdded and onResourceContentCommitted) should actually provide details of these resources that are supposed to be always in sync across all the developer tools (included the ones added by the extensions).
 
It would be reasonable to "do not duplicate the same listing and tracking efforts in multiple places" even more than now, e.g. to implement the getResources and onResourceAdded methods, and it would also make it simpler to better integrate the developer tools with each other (e.g. for the onResourceContentCommitted).

And so, unfortunately this issue (and Bug 1361121) is currently "on hold" for now, but it seems to me that some of the changes on the devtools side (which are currently in the planning stage) are going to make this possible and simpler in the future, by providing a kind of "unified resource tree" that these APIs could refer to.