[Tracking Requested - why for this release]: We should track this for 87 and possibly consider it for a dot-release ridealong in 86. Reasoning: the regressing patch landed very late-in-the-game on 86, with very little Nightly testing, and went pretty much straight-to-release, because we thought it was extremely targeted. (per bug 1692380 comment 7.) This bug report revealed that in fact it was not targeted & had some collateral damage, because the targeting API that we were relying on was actually not implemented in the class in question. This patch fixes that by actually making the check in question actually-targeted (at <marquee>, and not at other arbitary elements), to undo the collateral damage from bug 1692380.
Bug 1695578 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.
[Tracking Requested - why for this release]: We should track this for 87 and possibly consider it for a dot-release ridealong in 86. Reasoning: the regressing patch landed very late-in-the-game on 86, with very little Nightly testing, and went pretty much straight-to-release, because we thought it was extremely targeted. (per bug 1692380 comment 7.) This bug report revealed that in fact it was not targeted & had some collateral damage, because the targeting API that we were relying on was actually not implemented in the class in question. This patch fixes that by actually implementing the targeting API that we're relying on (so that the code in question is in fact targeted at <marquee>, and not at other arbitary elements), to undo the collateral damage from bug 1692380.