Specify what getAsString and getAsFile does when DataTransferItem is in the disabled mode

[rniwa]

DataTransferItem defines the disabled mode but the definitions for getAsString(callback) and getAsFile() doesn't check this state. As far as I read the spec, the intent here is for these functions to abort steps but that should be explicitly stated in the spec.

[annevk]

Isn't that specified by omission? It has to be in one of the two modes listed and otherwise steps get aborted? I agree that it could be clearer though.

[annevk]

And what I mean by clearer is that we could be more explicit about internal slots (such as mode) and how the value of those slots change over time.

[rniwa]

No, the current mode of the drag data store is independent of whether a particular instance of DataTransferItem still represents an item in the drag data store or not. e.g. you can be in read/write mode, and an instance of DataTransferItem may refer to an item that had since been removed. e.g. after calling clear on DataTransferItemList.

[annevk]

The way I read

While the DataTransferItem object's DataTransfer object is associated with a drag data store and that drag data store's drag data store item list still contains the item that the DataTransferItem object represents, the DataTransferItem object's mode is the same as the drag data store mode. When the DataTransferItem object's DataTransfer object is not associated with a drag data store, or if the item that the DataTransferItem object represents has been removed from the relevant drag data store item list, the DataTransferItem object's mode is the disabled mode.

is that the DataTransferItem's mode mirrors drag data store mode until it gets detached somehow. And the steps refer to DataTransferItem's mode, not drag data store mode.

[rniwa]

Oh, I see. That indeed is sufficient here.