Confirmed for 1.19.40
Finally fixed with the texture update in 1.14 yay
Why is this still reopened when it’s “fixed” for 1.14?
Why is this reopened when the snapshot isn’t even out yet?
WAI per this tweet by Searge:
The question about the VBO option in the latest snapshots came up a few times. It's been removed on purpose and VBO will now always be used. This is one of the first side effects of the ongoing work we do to improve the rendering engine. #JustBlaze3DThings
https://mobile.twitter.com/SeargeDP/status/1060455384471793664
Just tested again in a world created in 19w03c. Cannot reproduce at all. Made ceilings up to the height limit to no avail.
Edit: just tested with slabs, glass, trapdoors, and stairs. Cannot reproduce for those blocks.
Just going to say that I can’t reproduce in 19w03c...
Cannot reproduce in 19w03c. Please see attached screenshot.
How is this reopened when it’s fixed for a future version?
^^
This bug report is now invalid due to the particle being removed in 17w47a.
All except for three people have been added in 17w31a.
If the server is running 1.11.1, its best to upgrade it to 1.11.2.
PC crafters can rest easy, too: we aren’t planning to remove quasi-connectivity from that version. But stay tuned for other exciting developments there, too!
http://mojang.com/2016/08/whats-happening-with-redstone-on-pocket-win-10/
Welp, I suppose that's the final nail in the coffin for people wanting to get it fixed. This report can finally be "resolved as Won't Fix".
PC crafters can rest easy, too: we aren’t planning to remove quasi-connectivity from that version. But stay tuned for other exciting developments there, too!
http://mojang.com/2016/08/whats-happening-with-redstone-on-pocket-win-10/
Welp, I suppose that's the final nail in the coffin for people wanting to get that fixed. This report can finally be "closed".
Although I'm not the person you're looking for, allow me to explain.
The user was supposedly attempting to connect to a server that is seen on https://sessionserver.mojang.com/blockedservers, but since the server that the user supposedly connected to violated the EULA, it was blocked. This no longer occurs as of 1.9.3-pre3 (the current prerelease).
Late to the party for me, but congrats on making the 100,000th bug report!
Confirmed for 22w44a