Create an entry in 2+ languages with a grid field with some data. Go to one of the entries and click “Remove Translation”. Load any other language, and the grid data will have been deleted too.

Relevant function trace:
* ext.publisher.php->before_channel_entry_save()
* $this->entryEvent->emit(‘publisherDeleteTranslation’, $entryId, $languageId);
* EntrySubscriber.php->onPublisherDeleteTranslation()
* $entry->delete($entryId, $languageId);
* Entry.php->delete()
* $this->entryEvent->emit(‘publisherDeleteEntry’, $eventArgs);
* EntrySubscriber.php->onPublisherDeleteEntry()
* $fieldHandler->call(‘deleteEntry’, $args);
* which finally calls `GridType.php->deleteEntry()`, which deletes all grid rows for this entry

A potential hacky fix for this might be to adjust `FieldHandler.php->call()` to check:

if (isset($parameters['languageId'])) {
    $parameters['skipEntryDelete'] = true;
}

at the beginning, and then in `GridType.php->deleteEntry()` we can check:

if (isset($params['skipEntryDelete'])) {
    return;
}

GridType.php->delete would also need to be adjusted to accept the parameters that are passed:

public function deleteEntry(array $params = [])

so it skips the entire grid entry deletion event in that case. That at least seemed to work in my test case, but you’d have a better sense of side-effects of this sort of change.

Attached image shows rows in the publisher and grid tables before/after for languages 1 and 4 and removing the translation for lang 4.