The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: jrmd <jrmd@git.wordpress.org>
Co-authored-by: Mamaduka <mamaduka@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

👋 Thanks for your first Pull Request and for helping build the future of Gutenberg and WordPress, @jrmd! In case you missed it, we'd love to have you join us in our Slack community.

If you want to learn more about WordPress development in general, check out the Core Handbook full of helpful information.

Thanks for contributing, @jrmd!

I just realized that we also need to handle the forward delete case. Here are the reproduction steps:

1. Add two paragraphs.
2. Disable the second paragraph - wp.data.dispatch('core/block-editor').setBlockEditingMode( wp.data.select('core/block-editor').getBlocks()[1].clientId, 'disabled').
3. Place a caret at the end of the first paragraph.
4. Press forward delete. Fn+Delete on Mac.
5. Expected: The disabled second block should be merged into the first block.
6. Actual: The disabled second block is merged.

Ahh thanks @Mamaduka I actually tried to see if that test case was valid using the accessibility keyboard but it didnt work; so TIL about fn+delete :)

Updated the logic, and also added unit tests and fixed the failing unit tests :)