Bugzilla

I'm not familiar with the code in the patch that landed here, or the internal details of the `interactive-widget` stuff  (other than having run up against it when diagnosing bugs), or how likely sites are to request one or the other; so I'm happy to defer to your judgement. :)

The only possible-pitfall I'd note from the proposed backout would be: I think (?) it'd mean this bug would regress **for users on release versions** until we ship bug 1916002.  (As you say: "this issue [is] less severe with the new default `resizes-visual` mode" -- that's only the default on Nightly for now, pending bug 1916002 to let it ride the trains to release.)  i.e. whatever benefits we got from the patch that landed here would be lost for release users, until we're ready to ship `resizes-visual` to release.

(You're of course already aware of that & perhaps timing your proposed backout accordingly, but I wanted to mention that just in case.)

I'm not familiar with the code in the patch that landed here, or the internal details of the `interactive-widget` stuff  (other than having run up against it when diagnosing site-report bugs), or how likely sites are to request one or the other; so I'm happy to defer to your judgement. :)

The only possible-pitfall I'd note from the proposed backout would be: I think (?) it'd mean this bug would regress **for users on release versions** until we ship bug 1916002.  (As you say: "this issue [is] less severe with the new default `resizes-visual` mode" -- that's only the default on Nightly for now, pending bug 1916002 to let it ride the trains to release.)  i.e. whatever benefits we got from the patch that landed here would be lost for release users, until we're ready to ship `resizes-visual` to release.

(You're of course already aware of that & perhaps timing your proposed backout accordingly, but I wanted to mention that just in case.)