Bug 1708018 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.

Original comment by
on 
(In reply to Sam Foster [:sfoster] (he/him) from comment #4)
> Its possible this is actually a good candidate for an allowed-dupe, and I can land with the moz.build changes, but leave the allowed-dupes.mn entry - with a new bug filed to track it beyond these proton/MR1 changes.

This WFM. ISTM the report-site-issue builtin extension could just be merged into the main product at this point, I don't know that there's any benefit to it remaining an extension. Then this problem would go away.
Revision 1 by
on 
(In reply to Sam Foster [:sfoster] (he/him) from comment #4)
> Its possible this is actually a good candidate for an allowed-dupe, and I can land with the moz.build changes, but leave the allowed-dupes.mn entry - with a new bug filed to track it beyond these proton/MR1 changes.

This WFM. ISTM the report-site-issue builtin extension could just be merged into the main product at this point, I don't know that there's any benefit to it remaining an extension. Then this problem would go away. (But obviously we shouldn't try to accomplish that in this bug.)

Back to Bug 1708018 Comment 5