TwinShards

@Brain180 I mentionned in the 1.17.1 screenshot i could type with the font in prior versions and snapshots with a normal spacing. Yes that was kinda lazy for me to not provide a vanilla screenshot but i didn't want to potentially screw up my options and stuff.

Anyway MMK21 was nice enough to provide a vanilla version so Ty.

So annoying glitch. This issue has been a thing for i think, since the commands have been rewrite to be easier i do not remember in which version though.
Still present in latest 20w07

Hi violine1101, i am sorry to put that here, but i do not know where i could get in touch with a mod to re-open a "resolved" issue.
So once a mod will see this, could you please re-open https://bugs.mojang.com/browse/MC-98308 ?
Ironically the issue cameback 1 snapshot after my check and didn't check for a while...

I have just re-check before the full release and found out in version 19w41a the bug is back and technically worst.
*The transparency is fully gone even on non-enchanted piece of armor.

This has somewhat been fix, going the opposite way.
There was a glitch where you couldn't open Elytra while having upward velocity. So in X snapshot for 1.15 you can open it much sooner.

So i'll say like Paul, this works as intended.
How would start flying if you couldn't even open your Elytra while on flat groud?

I have just check in 19w40a and it seems like the transparency is working while enchanted now.
It probably got fix with the new rendering.

I will call this "Fixed" in the latest Minecraft 1.14 Snapshot: 18w45a

@Muhammet_Kurt I'm not sure, builded a new gaming build. So i can't really tell if there is big lag-spike of death.
But with a bit of redstone ~25 redstone clocked with a comparator, i can still see a very low amount of lag-spike. 

I will update affected version because i assume it is not fixed.

Still, a Static state and a flowing state are 2 different state. Which should trigger the observer.

I just did a quick video, just to show you it doesn't even detect any block state changes (lava/water going to a flowing state)
https://youtu.be/DU192xbPOnM

Observers are supposed to detect block state changes, not random ticks And it's what it was doing before 18w10d.*
The observers was detecting the change from static state to flowing state. Now it doesn't not anymore. (It doesn't not detect even when it's visually going to a side flowing state)

The real issue with MC-109829 was the fact that water/lava kept going to a flowing state/non-flowing state, because the redstone behind the observer kept retriggering the water/lava front the observer.
Here this issue is the fact that it doesn't even detect a single block state changes.

@Neko. the reported "bug" of MC-109829 didn't got 'fixed' voluntary.

It got 'fixed' though, it more like got buged at the same time of the water update behavior ...

I really feel someone like @Grumm or @Dinnerbone or else should say his word about this.
Yes, some, SOME peoples reported this feature. And it's only because they don't work really much with redstone, that is why they are complaining about the fac it does that.

Do you remember around 1.12, the Random tick update was patched on lava/water (because of the issue that lava/water couldn't be use with water to make Redstone clock but it was rapidly reverted because some lava/water in cave could stay static)

See this part of this video: https://www.youtube.com/watch?v=FVr28VwAOkM&t=124s
(up to 2:46)

So all for saying this doesn't not work has intended now and this must get fix.

By the way, why are you sticking my bug report has related to MC-109829 It's not related.

My bug report is the total oposite of this one*

Confirmed 18w14a/b
Side note:
Now from 18w10d to lastest;
The water/lava doesn't make block update to the observer because of the new Water mechanic.

I would be really pissed off if Minecraft 1.13 came out without getting this fixed!
It's so easy to make Stone Generator with 1 Observer ：）
Last version with water/lava making block update is 18w09a
Here is a quick view of what is happening now:
https://youtu.be/sM7fzp62V0E
*Accidentally left my micro off, no voice sound.

I'm telling this was intended in the past " Because there is not enough lava"
And it's totally the same for Water.
However. I guess the best would be: when the lava/water can't be transformed, it would just get crush and be replace by the flowing master.
(Lava above water if can't make stone, lava crush the water block and because there is other water from the flowing water, it would make cobblestone)
And when lava can't make cobblestone it would get crush by water.
It's just my opinion.

Ｃｏｎｆｉｒｍｅｄ， １８ｗ０９ａ
My issue report is related to this one, and i'll update it when i check. I'll not confirm for further version.

［Ｍｏｄ] Ｍｉｃｈａｅｌ, i'm going to check if the same "Client thread/WARN" happen aswell...

I confirm, this is issue is 100% related to this one. See below what the Log-Output was writing:

16:48:06 wj Client thread warn Something's taking too long! 'root.tick' took aprox 139.149578 ms
16:48:06 wj Client thread warn Something's taking too long! 'root' took aprox 185.002342 ms
16:48:06 wj Client thread warn Something's taking too long! 'root.tick' took aprox 122.662909 ms
16:48:06 wj Client thread warn Something's taking too long! 'root' took aprox 166.025208

Note: I noticed when the pie sort of " over load" it will only show the following:
ｔｈｅ ＂ Ｌｅｖｅｌ＂ ｉｓ ｓｕｐｐｏｓｅ ｔｏ ｂｅ ｔｈｅ Ｒｅｎｄｅｒ
-Level: ８５，００％ ５８．５０％
gui: 15% 10%
unspecified: 0.36% 0,24%

Doesn't seem to still occur (18w08b)

This bu report is more likely duplicate of mine... MC-123263

Can confirm for 1.12.2...
And i did a video to show:
https://youtu.be/XCTSDp0dXiM

I'm still waiting confirmation of where could i upload the world...

*Can't upload here... It told me it's over 10.00MB

It does 24.6Mo. (in Zip)
Want i upload it somewhere else? (But where)