I've confirmed it works for my code block, too. 👍

I ended up using the hasBlockSupport function from blocks package for the check, something like so, but don't think it makes much difference.

import { hasBlockSupport } from '@wordpress/blocks';

	const useLightBlockWrapper = hasBlockSupport(
		'core/code',
		'lightBlockWrapper',
		false
	);

Hey @mkaz or @beaucollins,

I don't know if I'm going crazy here, but could see if you can replicate the follow behavior in a code block? I'm running Chrome + Gutenberg 7.9.1 and this plugin is disabled and this is the behavior I get:

Uploaded Gif to imgur since github was yelling at me...

To replicate:

1. Put cursor on a line with text preceded by a blank line
2. Enter following keystrokes:
   1. Left Arrow
   2. Down Arrow
3. Result: it skips you down a few lines

@allejo I've merged #20 into this branch and tried to resolve conflicts, but I'm getting an error now when Gutenberg is active:

We need to adjust the usage of plainTextRef.

Yea I'm getting the same error, let me take a look

Alright @westonruter, 6aa9eb2 should fix things in a BC way for Gutenberg 7.9.

@allejo One more thing… In the console I'm getting a warning when Gutenberg is deactivated:

Warning: React does not recognize the highlightedLines prop on a DOM element. If you intentionally want it to appear in the DOM as a custom attribute, spell it as lowercase highlightedlines instead. If you accidentally passed it from a parent component, remove it from the DOM element.

Destructuring the incoming props should resolve that warning, f5eca87. I couldn't think of a different name other than props_ though, so you're welcome to change that.

That works well!

@allejo I do not see the same behavior using Gutenberg 7.9.1 and code block, it all seems to work as expected for me Firefox + Chrome.

Thanks for checking @mkaz, I'll take a look to see if I can figure out what's going on on my end!