The Bug:

Relates to MC-116877.

When you have a block with a block state in item form and place it, the entity collision checking ignores the block state. This can lead to some strange valid or invalid placement conditions for certain blocks that have different collision boxes depending on the block state.

Steps to Reproduce:

1. Build the configuration as seen in MC-221256.png.
2. Give yourself a slab with the "double" BlockStateTag using the following command:

   /give @s end_stone_brick_slab{BlockStateTag:{type:"double"}} 1

3. Position yourself on the edge of the Enchanting Table.
4. Place the slab on the side of the Gray Wool block to the left of the Enchanting Table.
   The block is placed even though it collides with the player's hitbox.

Examples from Original Report:

If you use this command:

/give @s chain{BlockStateTag:{axis:"y"}} 1

and aim at the side of a block with the item, the entity collision checking thinks that the chain will be placed horicontally even though you place it vertically. This means that for exmple when you are standing on the edge of a non-full block like an enchanting table you will be able to place the chain inside yourself when aiming at the side of a block.

If you use this command:

/give @s end_stone_brick_slab{BlockStateTag:{type:"double"}} 1

and aim at the floor you would usually place a bottom slab, but with the item you will place a double slab. However the entity collision checking still thinks you are placing a bottom slab allowing you to place the double slab inside yourself when jumping of standing on the edge of a non-full block like for example an enchanting table.

If you aiming at the side of a block with the chain that places a vertical chain and standing like this you can see in this screenshot, you will not be able to place chain even though it wouldn’t be insde you, if you are aiming at the floor however it will work.

This affects every block with any block state that changes the collision box.