I don't think we're anywhere close to a point where transparent wrappers (js::CrossCompartmentWrapper) will go away, or can be ignored by SM devs. Even after Jan's changes, we'll still use them for lots of things (including Chrome->Content XrayWaivers).
For stuff that's super edge-casey, it may be ok to punt and throw, but we don't want to get ourselves into a situation where CCWs gradually stop working because devs stop caring about them. They're an important engineering tool, and I don't doubt that we'll continue to rely on them and find new uses. On Fri, Sep 7, 2018 at 2:11 AM Lars Hansen <lhan...@mozilla.com> wrote: > Thanks. Same-origin should be plenty good for what I'm doing. > > In the mean time, trapping / throwing when attempting to unbox an anyref > that needs to be unwrapped is probably fine. > > --lars > > On Fri, Sep 7, 2018 at 11:05 AM, Jan de Mooij <jdemo...@mozilla.com> > wrote: > > > On Fri, Sep 7, 2018 at 10:47 AM, Lars Hansen <lhan...@mozilla.com> > wrote: > > > >> So: what's the story, and what's the status? > >> > > > > Bug 1357862 will eliminate a lot of wrappers (it requires some Gecko > > changes still before we can enable it), but it will only get rid of > > same-origin wrappers at first. There has been some discussion about > > follow-up work to eliminate more wrappers, but I don't know if/when that > > will happen. > > > > Jan > > > > > >> > >> --lars > >> _______________________________________________ > >> dev-tech-js-engine-internals mailing list > >> dev-tech-js-engine-internals@lists.mozilla.org > >> https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals > >> > > > > > _______________________________________________ > dev-tech-js-engine-internals mailing list > dev-tech-js-engine-internals@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals > _______________________________________________ dev-tech-js-engine-internals mailing list dev-tech-js-engine-internals@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-tech-js-engine-internals
