gecko-dev/dom/manifest
Marcos Cáceres 1118e89526 Bug 1563460 - Collect console messages generated by processing manifest for Dev Tools r=baku
This gets rid  of the sending warnings to the browser console. Instead, when the processor is explicitly asked to do so, it now collects spec violations into a `moz_validation` member.

To access the new manifest member, you can now pass a second argument to `ManifestObtainer.contentObtainManifest()` like so:

```
const manifest = await ManifestObtainer.contentObtainManifest(
      this.targetActor.window,
      { checkConformance: true }
);
manifest. moz_validation; // 🎉
```

Differential Revision: https://phabricator.services.mozilla.com/D36885

--HG--
extra : moz-landing-system : lando
2019-07-09 02:33:39 +00:00
..
test Bug 1563460 - Collect console messages generated by processing manifest for Dev Tools r=baku 2019-07-09 02:33:39 +00:00
ImageObjectProcessor.jsm Bug 1563460 - Collect console messages generated by processing manifest for Dev Tools r=baku 2019-07-09 02:33:39 +00:00
Manifest.jsm Bug 1561435 - Format dom/, a=automatic-formatting 2019-07-05 10:44:55 +02:00
ManifestFinder.jsm Bug 1561435 - Format dom/, a=automatic-formatting 2019-07-05 10:44:55 +02:00
ManifestIcons.jsm Bug 1561435 - Format dom/, a=automatic-formatting 2019-07-05 10:44:55 +02:00
ManifestObtainer.jsm Bug 1563460 - Collect console messages generated by processing manifest for Dev Tools r=baku 2019-07-09 02:33:39 +00:00
ManifestProcessor.jsm Bug 1563460 - Collect console messages generated by processing manifest for Dev Tools r=baku 2019-07-09 02:33:39 +00:00
moz.build Bug 1535353 - update Core :: DOM: * bugzilla product and component meta data in moz.build files after reorganization in bug 1533440 r=hsinyi 2019-03-17 23:13:22 +00:00
ValueExtractor.jsm Bug 1563460 - Collect console messages generated by processing manifest for Dev Tools r=baku 2019-07-09 02:33:39 +00:00