Leather horse armor no longer uses old texture when using programmer art

This is because leather horse armor was added after the texture revamp.

Well, the old leather horse armor texture was added in early snapshots of 1.14 (19w08a). But in the Pre-Release 1 of 1.14, they updated the texture to be the same as the other horse armor types.

True, DrownedZombie, but it should still be using the classic texture if one is using the Programmer Art Resource Pack!

As was already said, leather horse armor was added after the texture update, thus there is no old texture for it.

bedrock edition had a texture for leather horse armor in the old style in 2016 (0.15.0), if crying obsidian can have its old texture despite being "implemented after the update" why can't leather horse armor do the same, both had preexisting textures not on an item in the game, both got implemented after the texture update, only one gets its preexisting texture?

Hello, would it be possible to reopen this one as its own standing ticket? The original post is not articulate at all on the issue, and I would be happy to help update the description with new evidence.

In the time after the resolution of this ticket, Mojang choices suggest that this special case is actually not a duplicate of MC-169889:

As has been pointed out, old textures not from immediately prior to the Texture Update have been added to Programmer Art (see crying obsidian). Similarly, leather horse armour has been in the Bedrock Edition since 2016. Old textures already exist there, ready “for restoring” (the definition provided in MC-169889). This sets it apart from the likes of MC-159632 despite similar wording on the tickets.

Furthermore, the recent fixes for MC-280047 and MC-280278 demonstrate that additions need not be drag-and-drop for inclusion in Programmer Art. In fact, the 1.21.5 cycle demonstrates an openness and willingness to put in effort, such as the re-creation of previously generated spawn egg textures—some of which never previously existed on their own.

Please consider rectifying the current erroneous resolution. I acknowledge that reopening does not in any way guarantee a fix (I’ve seen that before). But for the integrity of bookkeeping, we ought to set the story straight by giving this ticket the opportunity to stand on its own in the current context. Thank you!