DropZone component no longer provides x and y position

[talldan]

Describe the bug
(Originally reported in the Making WordPress slack: https://wordpress.slack.com/archives/C02QB2JS7/p1591999141128800)

The DropZone component no longer provides x and y position to its callback.

It looks like when DropZone was rewritten to use a hook an optional withPosition prop that defaults to a falsey was added, possibly as an optimization:

gutenberg/packages/components/src/drop-zone/index.js

Line 24 in f15b91c

withPosition,

The DropZone component doesn't have a way to set this value, so since this change x and y are not provided:

gutenberg/packages/components/src/drop-zone/index.js

Lines 67 to 73 in f15b91c

	function DropZoneComponent( {
	className,
	label,
	onFilesDrop,
	onHTMLDrop,
	onDrop,
	} ) {

To reproduce
Steps to reproduce the behavior:
Reproduction is a little tricky, as it requires implementation of a drop zone.

Expected behavior
DropZone continues to provide x and y position data by default.

[ellatrix]

Do you mean this? #19514 (comment)

Either way, I think this was part of the 5.4 release? #20185 (comment)

[talldan]

@ellatrix I think it was that PR. As you say, looks like it was already shipped in 5.4, so perhaps this isn't a 5.5 must have.

[talldan]

This looks like the line:
https://github.com/WordPress/gutenberg/pull/19514/files#diff-af960f1a0848b34c0c03399a679e8c4dR143

I think it should be a pretty easy issue to solve, we'd need to expose the withPosition prop for the DropZone component. Possibly default it to true for backwards compatibility.

I can put together a PR.

[talldan]

Oh wait (sorry for multiple messages), I see what you mean now, that this is a separate position object that only provided the edge being dropped to and was only used in the drop events.

So, looks like it needed to be removed from the docs? I'll make the focus of my PR in that case.

[talldan]

#23577 updates the DropZone readme.