On 4/18/18 1:54 PM, Gijs Kruitbosch wrote:
Err, so it seems a side-effect of this (which wasn't very obvious to me when this was posted) is that it's now no longer possible to change a ..idl file for a JS component in an artifact build and have it "work".
So to be clear, this is a case in which you have an IDL-declared thing that is only implemented in JS _and_ only called into from JS, right?
Given that we're also not supposed to be making new JS-implemented webidl things, what's the long-term plan for artifact build support for changing JS-implemented interfaces?
For the specific case of "always known to be JS to JS" calls, why are we using an IDL-declared interface at all, if I might ask?
-Boris _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
