The integration test I just attached confirms that this change caused the problem: it fails on current trunk, and passes if one changes `additionalProperties` in the code linked to on searchfox above from `false` to `true` (though I don't know if other things should be changed in addition to that to make it a safe change). It's derived from one of the existing tests, but with the JSON replaced by something extremely close to the exact JSON that's on experimenter for the QA test right now. This is overkill for just testing the additional property thing, so it might not be what really wants to land.
Bug 1791163 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
The integration test I just attached confirms that reverting the change mentioned above would fix this problem: it fails on current trunk, and passes if one changes `additionalProperties` in the code linked to on searchfox above from `false` to `true` (though I don't know if other things should be changed in addition to that to make it a safe change). It's derived from one of the existing tests, but with the JSON replaced by something extremely close to the exact JSON that's on experimenter for the QA test right now. This is overkill for just testing the additional property thing, so it might not be what really wants to land.