Also: emilio noticed in a quick test that the patches-that-have-already-landed here may have fixed the originally-affected-site here. Given that, and to keep things simpler for tracking purposes (now that we've just crossed a version-number threshold), maybe it'd be best to close out this bug, and spin off a followup to get the remaining patch landed? (You can migrate the existing phab revision to the hypothetical new bug, just by editing the "Bugzilla Bug ID" field in the edit-revision field at https://phabricator.services.mozilla.com/differential/revision/edit/226212/ )
Bug 1923208 Comment 38 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Also: emilio noticed in a quick test that the patches-that-have-already-landed here may have fixed the originally-affected-site here. Given that, and to keep things simpler for tracking purposes (now that we've just crossed a version-number threshold), maybe it'd be best to close out this bug as fixed-in-134, and spin off a followup to get the remaining patch landed in the 135 nightly cycle? (You can migrate the existing phab revision to the hypothetical new bug, just by editing the "Bugzilla Bug ID" field in the edit-revision field at https://phabricator.services.mozilla.com/differential/revision/edit/226212/ )