Button with asChild and disabled still allows interaction on non-button elements

When a button is used with asChild and the child is a non-button element (`<a>`) disabled/data-disabled correctly set the right styles but click/keyboard interactions can still fire. It looks visually disabled but remains interactive. Could the button also block events for asChild elements to match native button disabled semantics?