Bugzilla

(In reply to Shane Caraveo (:mixedpuppy) from comment #15)
> There are a couple paths, 
> 
> 1. retain the functionality for extensions indefinitely. (I wouldn't want to go this route)
> 2. retain the functionality for extensions long enough to deprecate for extensions (which includes #3 below)

This bug, as described in comment 0, should be essentially FIXED via bug 1898445 (which added a pref that we can use for option 1 or 2 here^).  (Thanks gregp for the patch!)

I think the remaining work here is investigation to determine affected add-ons (comment 16) and to determine suggested alternative approaches (one approach may have been ruled out per comment 22); and then ultimately, a pref-removal in several releases when we're ready to deprecate fully.

In the meantime, I think we can consider this bug FIXED.  (It's not really accurate to have it tracked as a still-open regression causing extension breakage in 128 at this point, now that we have bug 1898445 landed.)

Hence: closing as fixed-by-bug 1898445, but we can still use this bug for discussion/investigation as-needed, or file separate bugs for that if folks prefer.

(In reply to Shane Caraveo (:mixedpuppy) from comment #15)
> There are a couple paths, 
> 
> 1. retain the functionality for extensions indefinitely. (I wouldn't want to go this route)
> 2. retain the functionality for extensions long enough to deprecate for extensions (which includes #3 below)

This bug, as described in comment 0, should be essentially FIXED via bug 1898445 (which added a pref that we can use for option 1 or 2 here^).  (Thanks gregp for the patch!)

I think the remaining work here is investigation to determine affected add-ons (comment 16) and to determine suggested alternative approaches (one approach may have been ruled out per comment 22); and then ultimately, a pref-removal in several releases when we're ready to deprecate fully (which will want to happen in its own bug, to revert bug 1898445, essentially).

In the meantime, I think we can consider this bug FIXED.  (It's not really accurate to have it tracked as a still-open regression causing extension breakage in 128 at this point, now that we have bug 1898445 landed.)

Hence: closing as fixed-by-bug 1898445, but we can still use this bug for discussion/investigation as-needed, or file separate bugs for that if folks prefer.