edit: As of 0.14.2 arrows in the top or bottom of a door do not update when the door changes state. But it's unclear if the bug got worse or if this works as intended...
If an arrow is blocked by the window (upper half of a door), it will float in the air when the door is opened or closed. We expected the arrows to fall and stick in the ground when the door was opened. In contrast, arrows blocked by the lower part of a door do fall and stick in the ground when the door is opened or closed.
Related issues
is duplicated by
relates to
Attachments
Comments


Thank you [Mod] do !

No problem 🙂

Cleaning up all the old issues - please reply if this affects 0.9.3.

Can confirm for 0.10.4 (iOS 8.1.3). Arrows do not update when upper doors are opened/closed.

Confirmed on Samsung Galaxy S4 Android 5.0.1 MCPE 0.11.1 (June 11, 2015 version)
Despite my best efforts, I cannot shoot an arrow through a door. I suspect that this part of the bug report has been resolved so I have struck it out and updated the title
I can confirm that arrows that hit the top block (window part) of a door will remain floating in space when the door position changes (open/closed). I expected they would drop and hit the floor when the door was opened/closed similar to what happens to arrows stuck in the bottom block of the door or any other block when that block is removed.

Does this bug still affects 0.12.2?, if so, please reply.

Still affects 0.12.2 on Samsung Galaxy S4 Android 5.0.1.

Confirmed on Samsung Galaxy Note 5. Android 5.1.1 Version: 0.13.0

Confirmed on Samsung Galaxy S6 (SM-G920W8), Android 5.1.1, MCPE 0.13.0.
More specifically, this affects all types of doors (including trap doors) and affect them if they are opened by the player or redstone.

In 0.14.2 now arrows shot into the top or bottom of the door fail to update (i.e. drop) when a door changes state.

Affects 0.15.0. (Tested on Windows 10.)

Affects 0.15.1 (Tested on Windows 10.)

Confirmed for 0.15.6. (Tested on Windows 10.)

Confirmed for 0.15.90.2. (Tested on Pocket Edition.)

Fixed in 0.15.90.8 (0.16.0 beta build 5).