Axes always disable shields

i mean ye thats the idea of axes it do it always like see dream (a pro minecraft youtuber) and then come back

Can confirm in 21w03a.

Can confirm in 1.16.5.

Can confirm in 1.17.1 and 21w43a
Axes are supposed to have a 25% chance of disabling shields, increasing by 5% with each level of efficiency and increasing by 75% on a sprint hit.

Code analysis (Mojang mappings, 22w18a):
LivingEntity#blockUsingShield(LivingEntity) is called when damage dealt by another living entity is blocked by a shield. Player#blockUsingShield(LivingEntity) calls the boolean canDisableShield(), which is true for wardens and if the entity is holding an axe item:

public boolean canDisableShield() {
        return this.getMainHandItem().getItem() instanceof AxeItem;
    }

The core issue is that if canDisableShield is true, the function calls disableShield(true); this extra boolean true adds 0.75 to the base chance of disabling the shield, so the conditional if (this.random.nextFloat() < $$1) will be true every time, which means the shield is always disabled:

...
    @Override
    protected void blockUsingShield(LivingEntity $$0) {
        super.blockUsingShield($$0);
        if ($$0.canDisableShield()) {
            this.disableShield(true);
        }
    }

    ...

    public void disableShield(boolean $$0) {
        float $$1 = 0.25f + (float)EnchantmentHelper.getBlockEfficiency(this) * 0.05f;
        if ($$0) {
            $$1 += 0.75f;
        }
        if (this.random.nextFloat() < $$1) {
            this.getCooldowns().addCooldown(Items.SHIELD, 100);
            this.stopUsingItem();
            this.level.broadcastEntityEvent((Entity)this, (byte)30);
        }
    }

This boolean is probably supposed to be a check to see if the entity is sprinting or if it is a critical hit. Otherwise, there would be no reason to call EnchantmentHelper, and the disableShield() method could just be these three lines.

Note: Mob#maybeDisableShield(...) is actually programmed correctly (kinda, it is missing one line, to tell the player to stop using the held item). However, it is called in Mob#doHurtTarget(Entity) after hurting the entity, and in the case of the player, this would call disableShield(boolean) first and disable the shield 100% of the time in advance.

Edit: I believe that Mob#maybeDisableShield(...) is not being called when the player uses the shield because... the player is not being hurt. So this function is basically unused when the player is actually using a shield.

isnt this intended?

Probably not (see @unknown's comment).
Edit: I just tested and this did not happen in 1.10, so if this was an unannounced change this is probably unintentional.

Hey!
I've experienced this all the way back to the nether update on Java and Bedrock since the update came out, I didn't know this was a bug.

This is intentional

Did you even read the other comments? Additionally, you need a Mojang source stating it is intentional.