Dug up that apparently this was "fixed" in 3.10. So, uh, 7 years ago. Either it's back or never fixed. Just had a game where Yasuo just walked around for his shield, then dove me. I landed a crit Q as Aatrox, popping his shield, but just short of breaking it. He dies to turret aggro after killing me, bam EXECUTED.
Something similar happens during back animations I believe. Like if Lucian is backing and Janna gives him a 200 HP shield and Ezreal Q's him for 100 damage it TECHNICALLY didn't hit him and therefore the backing animation doesn't stop. Could be a similar issue here.
Rule of Bethesda applies
"There are no bugs, only features."
That has been intentional this entire time. Damaging a shield doesn't count as damaging the champion. It's why Malphite can back under enemy fire if his passive is up without being interrupted, and why one secret tip for ekko players is to pop a W ontop of themselves as they hit back as well. Shields seem to be coded to not count as part of the champion when taking damage but count as it's separate unit. So damaging a shield doesn't equal damaging the champion. Which I will admit is a pretty damn dumb thing to implement, but likely what riot's go to response will be to dismiss the issue with said rule of bethesda of this being entirely intentional.
Riot, they fix things but they kinda fail to fix them so they come back.
Invisible Nunu is still a thing that happens.
