I tested this on Window 10 with FF Nightly 67.0a1(2019-03-12), Beta 66.0b14, Release 65.0.2 and I can reproduce this issue.

this is no longer a regression

(In reply to Tim Spurway [:tspurway] from comment #4)

this is no longer a regression

Could you clarify what you mean by this? Per comment 1, we have a specific regression range identified. (This is a defect that was introduced by Bug 821955.)

I can see why release-management folks might not care to track it as a regression, since it broke a long time ago. But from a writing-the-patch perspective, it's extremely useful to have this labeled correctly as a regression, since it gives a strong hint about what code is broken [the code in the regressing bug's patch].

(I know we've got a "Regressed By" field coming soon, and maybe the semantics of the regression keyword will change when that field arrives [not sure]. But it's not here yet.)

Anyway - for now, I'm restoring the 'regression' keyword since it's still applicable per my understanding of what the keyword represents.

Hey Daniel - yeah, thanks for restoring it. I was just trying to clear it off the stack of things we are tracking from a release mgmt perspective. But you're right, it's a regression.

(In reply to Tim Spurway [:tspurway] from comment #8)

Hey Daniel - yeah, thanks for restoring it. I was just trying to clear it off the stack of things we are tracking from a release mgmt perspective.

Thanks.

In cases like this, I'd suggest that you instead clear the "status-firefoxN" flags, since presumably those are part of what's getting it onto your "look into this for the upcoming release" dashboard, and those flags are only really useful/meaningful for bugs that regressed recently, not 45+ releases ago.

--> clearing those flags now.

Reproduced on latest Nightly 73.0a1 (10.12.2019) on Windows 7.

I tested this on Ubuntu 18.04 with FF Nightly 73.0a1 (2019-12-10) (64-bit), and I can reproduce this issue.

This issue is still reproducible on FF Nightly 75.0a1 (2020-02-18) on Mac OS 10.14.

Hi,

Could reproduce this issue on Nightly 77.0a1 Win10 x64.

Regards,

This issue is still reproducible on FF Nightly 80.0a1 32-bit on Windows 10

SVGSVGElement::SetCurrentScaleTranslate checks that things have changed but if we
manage to update both translate values before we get here then we'll skip the screen update
that we need.

Also

• introduces a tear off for SVGSVGElement.currentTranslate so we hand out the same
  object as required by the SVG idl
• removes SVGSVGElement::SetCurrentTranslate as dead code
• removes mPreviousScale and mPreviousTranslate from SVGSVGElement as they are no longer
  necessary

https://treeherder.mozilla.org/#/jobs?repo=try&revision=ddb7a87e149550db3b19b465fd3cc3dabd048835

Reproducible on latest Nigthly 81.0a1 (2020-08-19) on macOS 10.14.

https://hg.mozilla.org/mozilla-central/rev/6e2a9067912f

Hi,

I tested this today on Windows 10 on Firefox Nightly 82.0a1 (2020-08-27) (64-bit) and the bug is still present. Should I have tested it tomorrow?

Regards, Flor.

Thanks, Florencia!

Indeed, it looks like the original STR are still broken, so there's something else going on here. It looks like the reduced testcase is fixed, though (for me at least), presumably fixed by the patch that landed here -- so for simplicity's sake, let's keep this bug closed and I've spun off a new one to track whatever's still broken about the original site / STR: bug 1661509

So: for verification purposes, please uses the reduced testcase (attachment 9051432 [details]) rather than the original site.

• Old/buggy results are for the purple rect to be against the left edge of the page,
• Expected results are for the purple rect to be offset some distance (about the same distance) from the left vs. top of the page.

Hi Daniel,

Thanks for your reply and all of the details. I agree with you, the reduced test case does work and is solved on the latest nightly version. I'll add myself to cc on the new bug to provide any kind of test that you may need in the future (and that I can provide ;D ).

Regards, Flor.

Hi Daniel and all,

I proceed to advance this bug too since bug 1661509 has been fixed. I hope this is ok.

Regards, Flor.