| commit | 1118e89526716c1c1f9bdc62cbe246fbe9287621 | |
| author | Marcos Cáceres <mcaceres@mozilla.com> | |
| Tue, 9 Jul 2019 02:33:39 +0000 (9 02:33 +0000) | ||
| committer | Marcos Cáceres <mcaceres@mozilla.com> | |
| Tue, 9 Jul 2019 02:33:39 +0000 (9 02:33 +0000) | ||
| tree | 487da6c8d1d03d6b02cb4cbdcae1448dce1e3dd5 | treesnapshot (tar.gz zip) |
| parent | e7e86f1bd81dedad1117121e4d31740254aa67af | commitdiff |
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
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