Affected versions

• Fx 69.0b9
  Fx 70.0a1

Affected platforms

• Windows 10 x64
  Windows 7 x64
  Ubuntu 18.04 x64

Steps to reproduce

1. Access https://react-sortable-tree.surge.sh/
2. Resize the Fx window so that it is smaller.
3. Grab a node and drag it to the bottom of the tree and out of bounds of the Fx window.
4. Drag the node back up into the webpage.

Expected result

• The node is added back to the tree.

Actual result

• The page goes blank.

Regression range
Will return with a regression range as soon as possible.

I couldn't find a precise regression range this is as close as I got https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=8941a9be9141409229814e2688d207a890e3121b&tochange=529782921812aaf0558fbb22384b3051174657d3 .

Botond, do you think this could be related to anything in Bug 1531535 ?

(In reply to Daniel Cicas [:dcicas], Release QA from comment #0)

3. Grab a node and drag it to the bottom of the tree and out of bounds of the Fx window.

It seems to matter which node you pick: I can reproduce the problem if I grab the root node ("title"), but not if I grab another node.

(In reply to Daniel Cicas [:dcicas], Release QA from comment #1)

I couldn't find a precise regression range this is as close as I got https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=8941a9be9141409229814e2688d207a890e3121b&tochange=529782921812aaf0558fbb22384b3051174657d3 .

I don't believe this regression range is accurate.

I can reproduce this bug as far back as Firefox 28 (from December 2013). Firefox 27 and earlier can't load the page in question so I can't test them.

Happy to take a patch for 70, but since this is already triaged and set to P3 priority I'm setting it as fix-optional.
That will remove the bug from weekly regression triage.