(In reply to Daniel Holbert [:dholbert] from comment #4) > Severity is tricky here; if this were on the way to release, it'd be clearly s2, but given that we have this behind a pref, let's say s3. > > In any case, we'll need to fix this before the pref rides the trains. Update: we turned off the pref for Nightly as well (bug 1877719 comment 20 - 22), so I think we can consider this bug FIXED by that change (just as we considered the similar YouTube issue in bug 1877719 to be fixed by that change). I'll add a note on the relevant bugs tracking the pref-reenabling to be sure we don't regress this at that point.
Bug 1897995 Comment 8 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Daniel Holbert [:dholbert] from comment #4) > Severity is tricky here; if this were on the way to release, it'd be clearly s2, but given that we have this behind a pref, let's say s3. > > In any case, we'll need to fix this before the pref rides the trains. Update: we turned off the pref for Nightly as well (bug 1877719 comment 20 - 22), so this now doesn't reproduce on any of our release channels by default, and I think we can consider this bug FIXED by that change (just as we considered the similar YouTube issue in bug 1877719 to be fixed by that change). I'll add a note on the relevant bugs tracking the pref-reenabling to be sure we don't regress this at that point.