Left-aligned YouTube block appears inside centered YouTube block added below it

[nickcernis]

Issue Overview

If a left-aligned YouTube block appears above a centered YouTube block, the centered block container holds the left-aligned YouTube block. I expected the left-aligned block to appear above the centered YouTube block instead.

It's hard to select the left-aligned block as a result — I have to click a very thin area just above the video to select it, and there's no visual indicator as to where this magic hit target is:

Clicking the video itself plays it instead of selecting the block.

Steps to Reproduce

1. Add a YouTube block. (I used this URL: https://www.youtube.com/watch?v=IprmiOa2zH8 )
2. Left-align it with the alignment control.
3. Add another YouTube block below it and leave it with the default centered position.
4. Attempt to select the top left-aligned video.

• Gutenberg 2.5.0.
• WordPress 4.9.4
• Twenty Seventeen 1.4
• Chrome 65.0.3325.181 (Official Build) (64-bit)
• macOS 10.13.3

Expected Behavior

Either:

• The left-aligned video block appears above the centered block unless there is other content between them.
• Clicking the video block once selects it, clicking it again plays the video.
• Clicking the video block always selects it; the video can only be played on the front end.

Current Behavior

As described above.

Screenshots / Video

As above.

Related Issues and/or PRs

Could not find related issues.

Todos

• Tests
• Documentation

[danielbachhuber]

Related #6634 #4127 #4010

[karmatosed]

I am not sure what design feedback is needed on this. Let me see if I can help confirm some expectations. You should be able to select any block. You should be able to play all video blocks in the editor.

[brandonpayton]

This appears to be a duplicate of #4764, but I cannot verify yet because of #10151 where a left-aligned YouTube block is very small and disappears when you try to select it. I'm self-assigning this issue so I can retest once #10151 is fixed.

[brandonpayton]

Now that #10151 is fixed, I was able to test this and confirm it is a duplicate of #4764. Closing this in favor of the earlier issue.