See bug 1530097 comment 17 - 18 -- I went through all of the dupes and webcompat issues associated with that bug, and I confirmed that they're all fixed in Nightly 110, almost certainly due to the fix that landed in this bug here (aside from a few of the webcompat cases where the site had also been updated so that the issue had also gone away in older builds).
Bug 1799111 Comment 10 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
See bug 1530097 comment 17 - 18 -- I went through all of the dupes and webcompat issues associated with that bug, and I confirmed that they're all fixed in Nightly 110 (and presumably 109 though I didn't test it), almost certainly due to the fix that landed in this bug here (aside from a few of the webcompat cases where the site had also been updated so that the issue had also gone away in older builds).
See bug 1530097 comment 17 - 18 -- I went through all of the dupes and webcompat issues associated with that bug, and I confirmed that they're all fixed* in Nightly 110 (and presumably 109 though I didn't test it), almost certainly due to the fix that landed in this bug here. * In a few of the webcompat cases, the site had also been updated so that the issue had also gone away in older builds, so those were fixed for other reasons, but the original issue presumably would also have been fixed.
See bug 1530097 comment 17 - 18 -- I went through all of the dupes and webcompat issues associated with that bug, and I confirmed that they're all fixed* in Nightly 110 (and presumably 109 though I didn't test it), almost certainly due to the fix that landed in this bug here. *In a few of the webcompat cases, the site had also been updated so that the issue had also gone away in older builds, so those were fixed for other reasons, but the original issue presumably would also have been fixed.