Trident clips into colliding blocks after breaking Pointed Dripstone or Sulfur Spike

Summary:
When a Trident is thrown at a Pointed Dripstone or a Sulfur Spike, it correctly breaks the block but fails to register proper collision with the solid block directly behind or underneath it. Instead of stopping on the surface of the colliding block, the Trident clips exactly 1 block deep into it. Depending on the angle, the Trident ends up either completely embedded inside the block or partially buried with only its tail visible. This issue occurs regardless of direction (whether the Trident travels vertically downward or horizontally into a wall behind the spike). A reliable way to reproduce this is by standing 4 blocks away and throwing the Trident at a single-block-high Dripstone or Sulfur Spike.

Steps to reproduce:

1. Place a single Pointed Dripstone or Sulfur Spike (1 block high) attached to a solid block.

2. Equip a Trident.

3. Stand 4 blocks away from the Dripstone / Spike.

4. Throw the Trident at it.

Observed results:
The Trident breaks the Pointed Dripstone / Sulfur Spike but clips 1 block deep into the adjacent solid block. It ends up partially or completely stuck inside the terrain.

Expected results:
The Trident should properly collide with the surface of the next solid block after breaking the Dripstone or Sulfur Spike, without clipping inside it.

_{original report:}
Most of the time a trident is thrown to pointed dripstone an error occurs, which is that after breaking the pointed dripstone the trident is inside any block with which it collides

My device is Moto G8 Power with Android 11